On the other hand, even with CPUID spoofing, if a DRM wants to check that it's running environment is sane, it would not surprise me to see timing consistency checks (if huge spikes occur at some point of time, it may indicate the process is being tampered with. Or that the process got descheduled or there are big loads on the computer, but we're talking about softwares that tend to take the assumption tempering is going on when in doubt so...)