This has nothing to do with the OS. A statically linked linux executable will likely run on any kernel from version 1 to version 4. The issue here is dynamic linking, and windows DLL hell has a name for a reason
Which libraries are you including in your description of a statically-linked binary on Linux ?
Finally, Windows DLL hell hasn't been a thing since the early 2000s, and even then, it was primarily only an issue with applications dumping shared libraries into the Windows system directories.
* systray icons/application indicators
* newer fontconfig versions support new config options which results in fonts being broken for apps that use older versions
* I think there is some issue around glibc locales handling if you use a different glibc
* systemd/logind/... DBus apis
Those were just some external interfaces that came to my mind. I'm sure there are many more.