I exagerate, but: win32 GDI, windows.forms, MFCs, ATL and that is just from microsoft off the top of my head. There are way more when you start looking at all the solutions that a typical user might actually have running on their machine.
Oh, I wish that were true. I have twice been a test automation engineer and stopped exactly that not being true for all widgets. Some are, but many of them, including some styles of buttons are not. A simple heuristic to tell is that when a UI widget does something the win32 can't, its probably not a win32 widget.
Even using UI inspection tools like Spy++ panels with .Net buttons that aren't backed by win32 buttons just show don't show up as an item is the tree of UI elements. There are also applications that just do silly things like use GDI, DirectX or OpenGL to draw a thing that looks like a button and isn't controlable of adjustable via external calls at all.
But on Linux we have 2 and people are complaining.
Btw, GTK+ apps look very close to Qt apps on KDE as KDE's Breeze engine has a GTK+ version.
Additionally, an open source windows paint (that parent comment asked for) will not look consistent go GTK+ apps as well.