Oddly content free
A server with the requisite power is easy, but nothing on the hard part:
How does that remotely-rendered stuff get displayed locally quick enough not to wipe out all productivity?
There is nothing more irritating than a machine that's a little bit behind on you, causing you to overshoot the adjustments all the time.
There's only about a 40ms latency window to do the entire round trip before it feels "slow", and while getting a ping that low isn't too hard, this needs an entire 1080p or higher (4k?) resolution screenful of rendered content to be delivered to lots of workers in various locations at the same time.
RDP doesn't really cope with that in my experience - at least, not on commodity networks.
It's perfectly fine for "do this series of commands" but horrible for "up a bit, down a bit, no, looks like too far nudge it back" types of adjustments that all visual (and presumably audio) creatives do all the time.
If they do not solve the latency problem, it simply will not be used.