No, this is very very rare on things that aren't Windows.
Lots of people say "registry corruption" when they mean "cruft"; over time apps register shell extensions and various other systemwide bits and pieces that gradually reduce UI responsiveness or break in strange ways.
No, it's not as rare as you think. Yes, it's because of the lousy design of the TCP/IP stack in windows.
There's nothing wrong with the network stack in Windows. NT has always had a first class network stack and they keep improving it with every release, as is normal for any modern mainstream OS.
PS: That Google link I assume was provided for humour rather than any real substance.
Two can play at that game:
What netsh winsock reset does is tear out DLLs, tear out various registry settings and mucks about with other system files.
Clearly you have no idea what you're talking about.
So there is no real distinction here between a Winsock reset and the equivalent operations in the other 2 big OSes. The difference is that whilst Windows holds its network configuration in the Registry (ugh), the other two do not. The operations being performed is otherwise pretty much identical.