I think the implication is that you deactivate the non-X3D CCD when gaming to get identical or better performance (higher clocks?) as the 9800X3D and then reactivate the CCD for productivity workloads. If that works, I think it is a viable strategy which you cannot do with the 9800X3D.
Edit: Now that I think of it, why wouldn't you do this as the default? It should get around the OS scheduling limitations and rarely does anyone game and work at the exact same time on the same computer.
Because the hardware is not capable of it. AMD provides a custom scheduler driver that's supposed to inject in games through the Xbox Game Bar, which sets the affinity of the detected game to run on the more appropriate CCD for best performance. The caveats of this are obvious:
1. It needs the Xbox Game Bar to be installed, activated and updated
2. AMD and Microsoft need to issue updates for it to work (something which is not guaranteed to happen in the very long term)
3. You can't get the benefits of using both sides of the processor at once. It works better as an 8 core or 8 core+3D cache configuration, rarely if ever well together
You may manually assign processor affinity with a tool like Process Lasso, otherwise the only way to activate or deactivate CCDs is with a system reboot. Ryzen Master should be able to automate that process with a one-click I believe, but it is not a seamless experience.
There is no problem with the task scheduler in the Ryzen driver or any other CPU.
What actually exists is a lack of optimization in home PC software.
There is no such thing as a lack of CCD optimization in servers, because only server software knows how to deal with many cores.
Or servers have thousands of tasks at the same time that use several cores.
You seem to be contradicting yourself, because you say that there is no problem, and then you proceed to point out the exact problem, lol.
Windows is not optimized for this topology, and it is very likely that it will never be. Intel's thread director works around this issue seamlessly through hardware-based runtime feedback to the operating system by literally telling it where to issue and physically execute each instruction, something that AMD hardware is not currently capable of.