Some of that is also that what "native UI" means has shifted a bit. To look at Windows, Win95 had a thoroughly considered UI design that was very well adapted to both what it needed to do and the hard constraints on it. Win11 is... kind of a shitshow. (Are parts of it still from Windows 3.1? I haven't tried to track them down... but in Win10 there were a few dark corners.) It made sense to match the native UI in the Win95 days. It often doesn't now, it's simply not a target worth hitting. You could just use Win32 and target the older Win95 look, but apart from appearance issues, it was designed to work well in 1995, and we simply demand different things from our UIs now. Like support for touchscreens. Old Win32 apps are painful on touchscreens. (But, often, awesome without a mouse.) And those are real considerations, not oooh-shiny-new-thing designer BS.

Yes, modern Windows design is a bit of a mess, caused by both the designer bug of redesigning everything (we have had at least 3 different Windows design languages prevalent over the last 10 years) and Windows having to support extremely old legacy software. The second was almost nonexistent when Windows 95 was designed, they could have a true clean slate, so the comparison isn't as fair. But still, even with the abundance of native UI frameworks, the point holds true that no new software uses any of them, no matter if it's Win32 or WinUI. They could implement them very easily, and some hobbyist software does so, and it looks very native and in-line with the rest of Windows 11, but they choose not to.

And yes, the 3.11 ODBC file selector is still in Windows 11. Praise be to legacy components.