Here's what I'm talking about, in a nutshell:
Without a bootable rescue disk, you get these two scenarios:
Situation A:
1. You make snapshot with CTM.
2. Malware screws up some things, but Windows itself still works.
3. You run CTM from within Windows, and restore to the snapshot.
4. Problem solved.
Situation B:
1. You make snapshot with CTM.
2. Malware screws up Windows so badly that Windows won't even boot anymore.
3. You have no way to run a CTM restore, because you can't get into Windows.
4. You're out of luck.
With a bootable rescue disk, situation A remains the same, but for situation B you'd now have this:
Situation B:
1. You make snapshot with CTM.
2. Malware screws up Windows so badly that Windows won't even boot anymore.
3. You insert your bootable CTM rescue disk and restart the machine. Not using the hard drive at all, the machine boots directly from the rescue disk into a special CTM recovery environment that runs on the "bare metal" of the machine.
4. You restore to the snapshot.
5. Problem solved.
Therefore, if CTM isn't a real imager, and/or does not support creating a bootable rescue disk for you that contains a "bare metal" CTM recovery program, then CTM will be of limited usefulness.
It will only be useful in Situation A, not in the more serious Situation B.
Apple's Time Machine supports Situation A and B, because it does support doing a recovery from a rescue disk running on the "bare metal".
So am I going to have to use CTM and Comodo Backup, both? CTM for fixing stuff when Windows still runs, and CB for situations where Windows won't run anymore? Isn't that a big pain in the butt, to run two products and manage two sets of backups, just to cover both Situation A and B?