You are correct - the scheduling options are only the ones who you see and you can have only one schedule at a time.
Apart from SiteSync, other options that you might utilize are:
- deploy your database from staging to production, given that you don't have any data that comes from live (like forums, comments or statistics). If this is the case, then deploying the database would work perfectly for you. It can even be done without downtime - if you are in an NLB environment
- Use two Sitefinity instances that are load balanced, similar to what is described in the beginning of the thread, though this is not a very common practice. One of nodes will be public and the other one would be hidden and used only by your content editors. On the public node, you can disable the backend access with a firewall. Important thing is that the two instances should be able to see each other's servers, so that they can invalidate their cache.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items