systemd was actually inspired by launchd, not Windows. But I guess systemd, Windows and launchd do share one thing in common which is not having a bunch of bandaid shell scripts hanging the system together.
I don't think I've seen anyone complain about systemd's init system or service manager; it's always about the remaining 90% of systemd's scope and its tight coupling between all its parts (the tight coupling being the main problem).
Prevent dynamic linking?
Offer strong backwards compatibility?
Add support for a very wide range of hardware?
Put advertisements in the start menu?
Cause unexpected reboots for updates?
Send telemetry to the OS manufacturer?
Force users to get an online account unless they know the secret way to bypass the prompt?
Or is there a differentiator between Windows and Linux I am overlooking?
What you should look at is the difference between Debian and Devuan. Or between Debian and OpenBSD, to understand what the systemd project is doing, and how it’s doing it.
There are many of us that prefer Linux as it was before systemd.