If they’re going to use heuristics like that to get an approximate time, they could at least use it to validate connections to NTP servers or something that can actually sync the time properly. Get approximate time for initial sync, then contact a Microsoft server to get a more accurate time over HTTPS (which is what this supposedly meant to address), then use NTP to get accurate time and validate that it’s close enough, and only then when everything checks out, set the system clock to that time.