CPU power is not determined by only a clock speed.
I hope it handles higher plugin loads better, it better do otherwise I don’t know what I just spent tons of money on… 
It still makes zero sense. With basic system loads being equal between old and new system, the new arrived power goes where exactly? What is preventing from it being utilized?
When I’m done reinstalling everything else I’ll throw a few dozen Waves Mixhubs in the mix, see how Ryzen handles that. I used to max out with about 25 of them with my old i5.
Btw that video is pretty much useless. It just blames monitor or HDD for holding off CPU processing which makes zero sense. Isn’t your project loaded into RAM in its entirety? And all the processing happens between RAM and CPU? What does monitor or HDD have to do with it being able to do it? He’s rambling on about some magical processes putting a stick into a rolling CPU wheel, I’m not aware of anything that can do that.
I think that Pete guys who did Cubase testing is on to something, I think asioguard/cubase is not optimized for AMD CPUs and not behaving themselves. I understand that Steinberg team had no chance to work with these CPUs beforehand as even mobo manufacturers weren’t given a chance to prepare working BIOSes by AMD, so I hope things will get better/clearer in the near future.