There isn't anything for us to do here, so I'm closing this.
SIGH!!! That is literally what I wrote!
And ALSO that it might be something to work into the documentation Wiki as general advice (since it is just AS-IS) for enthusiasts. Because not everyone understands this and thus whilst DXVK is great, some might still get relatively bad performance since their drivers are just bad.
And btw. That Polaris vs. VK_EXT_extended_dynamic_state3 (Adrenalin 23.3.2) is a real thing. So before others step into that and think even DXVK isn't solving their issues, they might need to look into their driver stack.
Nothing extracted yet.
So to start of this is anything but a bug or failure. I have found after extensive testing something that the documentation might be happy with.
The so-called pinpoint of "peak-Polaris" performance is Adrenalin 22.11.2 on Windows where Polaris (GCN4) was still being a prime target and not moved to legacy state. And that prime target part specifically means that power management of this card was still done by the GPU's internal SMC. Later versions all regressed performance by either introducing new features or through security fixes. Additionally: system fans should become more quiet as well, since the CPU won't fight the GPU's internal SMC anymore over clock states, meaning Polaris can do what it is supposed to do and the system can cool down.
New features after 22.11.2 that DXVK can 'see':
However these features actually seem to make a game like GTA San Andreas stutter more with DXVK and Polaris and they are perhaps more suited for RDNA type of cards.
A combination of the following for Windows 11 is strongly recommended: