Earlier quoted context omitted.
> The Win32 daemon only provides coarse time adjustment. True in XP (it was a crappy SNTP implementation), but it was rehauled significantly in Windows 10/Server 2016 and above because of Azure requirements. It can now guarantee accuracy within 1 second at all times and even higher when the NTP server is local ( https://docs.microsoft.com/en-us/windows-server/networking/w... )
That’s still absolutely rubbish.
Knowing how accurate the timers within Windows is, this is actually not "rubbish" as you say, at least relative to Windows. Windows is designed for general computing, not for superprecise timings. Use Linux for that use case, not just shovel NTPD (spoiler: NTPD uses the Media timers in Windows, those are not definitely designed for that use case and there are too many applications that breaks if they are forced with the high-precision timers).
P.S. Linux can hold precise timings, but there are certain configurations that will break this assumption. Double check if this is important to you.