I swear windows is just full of sleeps and it doesn't matter how faster your system is.

It's more likely network calls that are taking a long time or timing out. A lot of developers insert function calls that under the hood hit HTTP servers, and it can take a few hundred milliseconds to stand up a new TLS connection and then however long it takes to send the request and get the response. It's also probable that the endpoints form an accidental microservice architecture in which case everyone is always hitting a different set of connections. This creates a perfect storm of having to reconnect to everything you hit occasionally which can create little slowdowns all over the place all without actually using CPU so it doesn't show up in any resource monitors.

HTTPS calls should be treated as calls to sleep() with undefined timings.