It's just a cleaner design, having implemented a tickless kernel for an RTOS. All of these "what is the actual timer frequency" questions that get more and more complicated as you're doing more (and other contexts are doing more) just sort of disappear.

What did you do for timer coalescing? If every thread can request a custom wakeup time then power consumption goes up. If wakeups are coalesced then what algorithm do you use to coalesce them, and how much movement in wakeup times do you allow? Depending on how you coalesce timers you can very easily find yourself reinventing the basics of what Windows does.

The Windows system also gives you a very cheap to read timer counter which is a nice attribute.

The Windows system is frustrating, especially for those who don't understand it, but it does have some excellent attributes.

That is your default Linux configuration. The distros tend to err on the side of functional systems but higher power use.

Start tweaking things like the stuff found in powertop. If your hardware is pretty standard Intel stuff you can get very low. For example, my Dell laptop will idle at 0.5 W with the display off, the SSD, USB, WiFi and PCIe bus all at idle.

That's about 5 days of power on battery. About equal to what any version of Windows can do with Modern Standby settings.

5 years ago I would have done that. And I did. A number of times. it never even approaches the runtime of Windows. Nowadays, I don't waste my time. I pay Microsoft for windows license, and do all my work in a Linux VM. Believe it or don't, this produces longer battery lives.