There's no fps difference and MT will be within run to run variance !
You need to change your boost mode.
Green is for CPPC off, Red is for CPPC on
View attachment 2560461
I don't understand exactly which point you are referring to.
If you disable all the CPPC settings, you will get less performances because the OS doesn't know anymore which core relates to which CCX cache, so it can't group threads that work on the same set of data to the cores that use the same cache, and this will inherently slow down cpu heavy algorithms as accessing the cache of a different CCX has a big performance penalty.
The processor performance boost mode is a setting that defines the speed with which a core will increase its frequency up to the maximum turbo boost mhz when a thread with a heavy workload requires it.
When CPPC is OFF, the CPU will use the P-states to manage each core frequency, and the P-states allow only two possible frequency states: Turbo boost ON, and Turbo boost OFF. So the "Aggressive" setting will be mapped to "Turbo boost ON immediately" and the "Efficient" setting will be mapped to "Turbo boost ON only if the thread specifically ask for the turbo frequency".
When CPPC is ON, the CPU has more granularity to choose the target core frequency, so the "aggressive" setting will be mapped to "Turbo boost ON immediately" and the "Efficient" setting will be mapped to "Start at an OS-calculated frequency and progressively increase up to theTurbo boost frequency".
All the options in that list are always mapped to one of the available choices following this table:
There isn't one of those listed choices that is not "functional" if CPPC is ON or OFF. In Windows 11 the default for both the "balanced" and "high performance" profiles is to use "Aggressive" as boost mode and I didn't get any performance increase by using a different value (I got performance increases by changing other power profile settings unrelated to CPPC).
But the performance penalty that you get if you disable CPPC is not related to the frequency of the cores. It's related to the ability of the cores on the same CCX to access the same cache instead of having to do an extra roundtrip to access the cache on the other CCX. Without knowing which cores are in which CCX , the OS can't optimize this cache access strategy.