Devs confirmed this was a bug iirc.
I disagree. You could easily add dynamic resolution in your example and then not achieve parity. What I want is developers using the unique hardware capabilities of the console and most of them actually do imo. Not to the absolute limit of the console, as this needs studios like ND, TC, ... mind you, but good enough that it shows effort and dedication.
I used the switch to make a exaggerated example and used loading to show how dumb parity is. I think parity is bad as a goal and of course with parity you are holding back a system. In the case of PS5 and Xbox Series X not by much, because while each console has benefits, ultimately they are very close. But still if you go for loading, resolution, ray tracing, framerate, ... parity, then by definition you are hindering one system. Which system you hinder will differ depending on the tasks.
For me it's a philosophy thing really, because I want each consoles to be pushed. Don't get me wrong, I won't get angry when parity is achieved. Happens for various reasons (budget, talent, time, ...), but I want developers to do their best with each version and for that they need to (try) use the unique customization and so on. Basically I don't want them to do the minimum as their goal and get away with it..