@Zeed disabling C-States, core parking and all of the power saving features will do a lot more for your latency than changing timer accuracy, if anything changing timer accuracy will make programs like LatencyMon a lot less accurate and might be the reason why you're seeing 'lower' latency numbers in it. Also don't use DPC latency checker for Windows 7 and up, it's not going to be accurate, LatencyMon is better, but I think you can affect its accuracy if you change timer resolution (which I presume is what that application is doing).
Ryzen is really good with power management, disabling C-states, using a fixed frequency, using the high performance power plan will only result in a minimal increase in power used.
@Scougar Oh, I agree, but Anadtech should have known better than to force HPET for all of their testing since it's non stock behaviour.
But on the other hand they did discover something neat, don't think that many people realized that HPET incurred a performance penalty after the spectre+meltdown patches, albeit if you think about it then it's obviously something that was going to be affected by the OS and microcode patches since HPET is a system call. HPET being higher resolution on Intel probably adds to the bigger performance impact the Intel platforms had.
On another note, AMD seems to have some issues with TSC accuracy
according to Agner Fog. Seems the way to mitigate that is to run Ryzens at a fixed frequency.