yeah amd power plans are aggressive, and have a very high min clock speed. I would love to understand their reasoning for this, but I accept the explanation. However as an end user I would for sure personally verify the response by checked ryzen master to be sure the cores are actually been parked as I Wouldnt be happy with a 1.3+ idle voltage.
Also even without low idle voltages c states should lower the voltage, so curious if the OP on that reddit page had tinkered with c states, the AMD rep may be suggesting that C1 to C3 states are all been skipped and going straight to parking.
My 2600x at non turbo voltages (and under clocking disabled) will have voltages of about 1.05v, (99% in power plan). However AMD's power plans have extremely aggressive p-states where by cpu's will spend really small amount of time at non turbo clocks when under any kind of load. I expect this all contributes to what the poster was seeing.
I personally dont notice any difference in responsiveness between microsoft and amd power plans, but the mean average idle voltage is considerably lower on microsoft so thats what I go with on my ryzen rig when its bare metal windows.
Some info here on it.
https://forums.guru3d.com/threads/t...ng-cooling-part-2.423134/page-17#post-5679536
So they made p-states more aggressive similar to what speedshift does on intel, one of confirmed reasons was for benchmarking (not surprised) but a real world game is also given as an example, if its actually improving actual real world usage then fair enough its hard to argue with that.
--update after finishing read amd rep post---
It seems confirmed p states are too aggressive, apps like hwinfo when polling are triggering xfr clocks so polling apps always see voltage for boosted workloads. I expect AMD will likely retune p-states or work with app vendors so they poll in a way to not trigger the behaviour.