> The threads “busy-wait” by running an infinite loop in a lower energy state on modern CPUs.

Doesn't that still use part of the process's timeslots from the OS scheduler's POV?