I've been playing with streaming app/game delivery techniques, and can see where a 10x pipe might help a lot.
There is a tradeoff that has to be made when you use an efficient interframe compression algorithm (i.e. x264 or mpeg). Latency becomes a factor, and you lose the ability to instantly seek/generate a given frame without keeping track of the ones that occurred prior. You also need specialized hardware or high performance CPUs on both sides. This also has issues tolerating high frequency visual changes between frames.
When using an intraframe technique (i.e. jpeg), none of the caveats apply, with the exception of 1 new one - The amount of bandwidth required is increased substantially if you intend to serve a sequence of these approximating a video (a la mjpeg).
I've had a lot of people give me grief for this idea, but I assure you a sequence of jpegs at 60fps looks like some kind of magic butter compared to the same encoded with more efficient techniques. Especially, when you put a human in the loop with an input device. You literally don't have to worry about the type of content at all. It just looks good always. The range of devices that can quickly encode (<10ms) jpeg at 30+ fps is surprisingly large (basically anything with a cpu made in the last decade).
I've almost memorized the most important bits of libjpegturbo by this point. Can't say I've even begun to scratch the surface on the likes of AV1, etc. Don't think I'd really like to just seeing the shadow of the damn thing. This kind of simplicity has benefits that can be hard to quantify.
Any time I can make some tradeoff like this, I like to think into the future. Is the speed of the average connection going to increase or decrease from this point? Do we need 100% of the planet to have 10GbE before we can begin exploring these ideas?