If you have updated the application, there is probably some .NET assembly optimization take place in the back ground. If UWF is enable, these optimizations are lost on reboot, and the optimizations happen again on each boot. When you disable UWF, the optimizations get written to the disk.
Here is some UWF write throughs for 2016 LTSB to test (Note the WinSXS and dotsvc\Policies will not work for LTSC 2019):
uwfmgr.exe file add-exclusion c:\Windows\System32\winevt\Logs
uwfmgr.exe file add-exclusion c:\Windows\WinSxS
uwfmgr.exe file add-exclusion c:\Windows\assembly
uwfmgr.exe file add-exclusion c:\Windows\dot2svc\Policies
uwfmgr.exe registry add-exclusion "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones"
uwfmgr.exe registry add-exclusion HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
uwfmgr.exe registry add-exclusion HKLM\SOFTWARE\Policies\Microsoft\Windows\WiredL2\GP_Policy
uwfmgr.exe registry add-exclusion HKLM\SYSTEM\CurrentControlSet\services\dot3svc
Are you using Shell Launcher to launch the WinForm application?