Late reply here but I have done this exclusively for a year.now - my folks live in the Philly market and get a good signal, but I am on the other side of a mountain and don't pick it up. Luckily they have 100 Mbps upload.
I used an old desktop with a 3930k in it because it had a Windows license tied to it, and so put some remote access software on it and Channels. The 3930k is great for core count and clockspeed for commercial skip processing, and I have it throttle down to 10% when not in use. I ended up adding a Quadro M2000 for transcoding. Then I have a storage spaces array for offsite storage of my Plex media library, the main server being at my house.
I will say these are things I added later that you should have for a 100% remote server:
- UPS, preferably power conditioning, with a USB or other monitoring connection to the server for graceful shutdown during extended power outages
- Wake on LAN turned on in the BIOS, and port forwarding to get the WOL magic packet through the firewall
- Labels on all the buttons and wires for over the phone troubleshooting if necessary (the person is letting your server live there rent free, if you enlist their help troubleshooting make it easy for them)
- Small 5 port dedicated network switch for any tuners and your server - this way if they are troubleshooting an issue with their internet, and they power cycle their router, it doesn't affect the connection between the tuners and server
- If possible, having another machine there helps. I parked an Unraid server there and it is nice because I have a way to remote into both if needed, and can send WOL packets back and forth (and troubleshooting things like pinging) between them
I have only used Channels locally on their network once, just to show them how it worked. They were happy with just using their TV's built in tuner, so it only gets remote use. Also, we have no issue having multiple desktops, laptops, tablets, and FireTV's at our house all tied to the remote server.
To add: I have noticed with only remote streaming that, while Channels does build a 'buffer' into the stream by slightly delaying playback when you tune to a channel, it is often not enough. Some shows will skip every 20-30 seconds while the buffer builds, to a lot of the time when tuning to a channel I just pause it for 5 seconds or so and then press play. I wish you could manually set a conservative buffer and have a countdown circle when tuning to a channel to let the user know what is going on, but the workaround works fine. I've noticed while on the phone with someone watching the same sporting event on cable that their stream is delayed behind mine, so I think the cable companies are just using a nice long delay for buffering.