I wonder if that is actually the Windows scheduler, or a combination of it and how AMD implemented NUMA. Reason I wonder is in multi-socket systems, which we use at work all the time, it has no issues with NUMA. In fact in things like Hyper-V you can tell it if a VM is allowed to span NUMA nodes or not, and in general it'll group threads from a process on a single node when it can. So I wonder if the issue was that the chips weren't properly exposing their NUMA topology to Windows so it can't tell which core is associated with which node, and thus do proper scheduling.TR3 should fair better with gaming this time around as it does not use NUMA, which the Windows scheduler has struggled with. So a game mode will probably not be necessary like past TR chips. I would expect similar boost frequencies as in Ryzen, probably will need some serious cooling to maintain higher clocks given how many cores these are expected to have though.
Either way if they don't use it on their new chips then it is problem solved and life is good .