Of all the issues I've had with emacs about 80% of them could be traced to running emacs on windows. Not through any fault on windows side mind (except possibly the insane decision to use a different path syntax).
Unless you want to claim the Unix developers deliberately chose the slash as a path separator to be incompatible with TOPS-10. That could be.
[0] http://www.os2museum.com/wp/why-does-windows-really-use-back...
Not inconceivable. After all Windows is called w32 in Emacs not win32 as is common everywhere else because RMS couldn’t bear to think “win” in association with MS!
I installed the official Windows binaries for GNU Emacs pretty recently, copied my elisp directory over, and for the most part things worked out of the box, but with a few inconvenient exceptions: taskbar pinning didn't seem to work properly due to the awkward emacs/runemacs distinction, and some things related to directory layout and navigation were painful due to assumptions of a Unix-style home directory clashing with Windows's user-directory layout. No WSL involved.