> isn't the network I/O going to outweigh the benefits of remote CPU cycles?

Not if:

   a) your network B/W is higher than your local disks (not as unusual as you might think, spinning medium is awful slow)

   b) the app you're using chunks up data in a reasonably efficient manner so as to not get bitten by latency issues (ffmpeg encoding likely meets that bar).