In my experience, both methods of synchronizing are unnecessary if you are not a pure consumer or exporter (say, from PDM/PLM to ERP). Automating these processes might feel good at first, but you are removing important "gates" from the process while introducing unmanaged variables.
Designers should start the day by "getting" the design files they are working on, and that should download only what is out of sync (if your GET operation isn't marked to "Force Override" local files). Unless you only work with layouts that are huge and always changing from one day to the next, I find it very questionable that you would need Workspace Sync. On top of that, any uploads you are automating will also remove your responsibility from check ins, in a way, which could be dangerous (files getting synch'ed/uploaded just for the sake of it, not when you are ready to submit).
For a user like you, as far as I see, you should only be synchronizing library files and templates, plus design data if that is managed through Vault. I would wipe the local workspace files every weekend, and do a "Get" on the top assembly or drawing you wish to checkout to work on every beginning of the day. Anything else you do not have checked out you can wait to synchronize after checking in your changes (work/edit, upload to Vault, re-Get the top assy/drawing, verify nothing is broken, move on).
