That's not how effective change works.
Effective change is implemented because a problem needs to be resolved, and those solving the problem understand what they need to do from the user perspective. Windows 95, as much as I hated it, was driven by changes requested by Windows users to make the OS more user-friendly—and it did. Regardless of how we old-school Mac users want to think of it, something like Win95 was necessary for the large-scale adoption of the home computer and everything that came with it. Win95 made DOS easy, and it allowed your parents to work on a spreadsheet from work after you played Doom. It was a seismic shift that affected the world; it was not solely change for change's sake.
What, precisely, is Liquid Glass solving? Sure, Apple could make the argument that it's a common UI, but the UX differs from device to device because the devices' purposes change. As I mentioned way back on another page, implementing a common design language across the devices makes sense—it would allow me to quickly move from an iPad to a Vision Pro to a Mac and generally know what I'm doing and how to navigate around each device. That's not what Liquid Glass is doing—it's simply one type of frosting on different types of cake.