No worries, Cooe :) I can only go by what I've read into the subject and the people involved that I've spoken to. I haven't seen the documents Kyle's seen, but I do trust my contacts.
From what I've been told it's not a case of the existing gaming brands only being allowed to be Nvidia-based. Companies could use their existing gaming brands for AMD and create a separate gaming brand for their Nvidia cards, it's up to them.
I'm honestly not sure how a company having separate gaming brands for Nvidia cards and AMD cards is anti-consumer.
The RTC bug wouldn't be improving his benchmark results though. If it was that particular bug, the reported clock speeds by Windows would change, but the actual performance when tested would not. Whether or not this OC is being applied due to a fault in RTC or not, unlike the common RTC innacurrate clock-speed reporting issues of yore; this overclock & the results it's pumping out look to be 110% legit which considering this isn't even Zen+ on 12nm HOLY FREAKING ****!!!!! (though I do have to wonder how well the Zen uncore can handle a BCLK cranked that high, 24/7) .
This bug affects most benchmarks on Ryzen even SuperPi. There's a good reason why Windows 10 on Ryzen isn't allowed at HWBot. That CPU was not running at 4.56 GHz Windows just thinks it was. Windows misread the BCLK coming out of sleep and from that point on everything was biased It's all smoke and mirrors on Windows 10 part