”
By executing those commands, one per day, we can cover a full CheckDB execution in phases. Another possible approach is execute the backups with the “CHECKSUM” option. This way we will be able to restore using the option “VERIFY ONLY” and do an extra level of verification. Anyway, we will still need the CheckDB.
”

1- CHECKFILEGROUP can combine both CHECKALLOC & CHECKTABLE of every table and indexed view in the filegroup so at some point we don’t need to use CHECKTABLE for any table inside the FG that has been targeted by CHECKFILEGROUP ; I just wanted to clarify this.

2- Another possible approach is execute the backups with the “CHECKSUM” option.

Not quite really, I’d stress that the only way to detect a corruption in a DB is to run checkdb. Instead of much talk , here’s a good blog

Some of approaches I suggest is to restore DB to another instance and run CHECKDB. You can run checkdb against a snapshot (ENT edition) , good idea if you have a mirror instance) but that’s not a true image of your production database.