I've never run into that issue with Ryzen Master, but only because using Intel's overclocking tools had already trained me to disable virtualization-based security. Intel's tools also had issues with that feature, and it took them a surprisingly long time to update their error messages to explain what was preventing XTU from running.

Aside from any driver signing issues, I think there's also an underlying common issue that the virtualization layer needs to pass through the CPU model-specific registers (MSRs) that are the hardware interface for tweaking power and clock limits.