The trouble with that idea is that data storage in the cloud would be needed for over 10 million, probably way over, receivers. That's a ton of space, who pays for it? I can understand that storing your individual timers on the remote that operates the receiver is a better business decision....
Assuming an average user's timers would represent 100KB of data per STB (which seems high to be honest, but it is a nice, round number), 10 million records might use as much as 1TB of space, or half of the capacity of one Hopper3's hard drive. Taking into account the content of the timers can be all text and would have lots of repeating records, I'd expect a 10:1 compression/deduplication ratio, so maybe 1GB of actual space used on Disk. That would be pennies per month for cloud storage.