Earlier quoted context omitted.
My point is that there are sanity checks built into the process. It's not difficult. There doesn't need to be a human verifying things there. Is the row count increasing over the previous backup? Check. Is the checksum different? Check. Is it non-zero? Check. And on and on. Stop making excuses and automate testing your backups.
so, when your check process does not report because it failed to run, how do you know? Do you have a monitor for your monitor? Does that monitor have a monitor? There is no reason not to automate your backup tests, but there is no reason not to eyeball the check is actually working from time to time.
MySQL is also pretty good about not starting if the data is corrupted for whatever reason. The process not starting is a pretty obvious alarm, too.
Checks are cheap. Better to automate your logic and invest in good monitoring and automation.