We usually suggest to leverage the API integration we have (so DDBoost, Catalyst or ReFS Blockclone) on a weekly base, as this is an almost "free" activity but it also has some limits: you always have an incremental from production, but on target you split the incremental chain having a new full "for free". This said, I can imagine the EMC guys are suggesting this so that each day is not dependent on the previous days but still we are talking about a fully deduped system, where a block is pointed at in multiple times, so any corruption in those blocks can impact every backup pointing at it. Synthetic fulls can save you from metadata corruption, but not from data corruption, this one could be solved only with active fulls, or synthetic "NOT" using dedupe API. But this would obviously make the synthetic full a heavy IO operation. If you are ok running a synthetic daily, I don't see any problem doing so.
EMEA Cloud Architect @ Veeam Software
Veeam VMCE #1