I updated my post above. You would also be disabling all other BPS Pro crons such as: …AutoRestore/Quarantine Cron, DB Monitor Cron, DB Backup Cron and Log file Zip and Email Cron, etc… If you do not care about the other automation in BPS Pro and want to do things manually then using an alternative host cron is fine in that case.
Another very simple possibility for this issue is that this is a time/timezone issue. ie the DB Tables are seen as being created after the Create Time timestamp for the DB Monitor Log. I will be able to verify that after logging in and looking at the Create Time timestamps in phpMyAdmin on that site.
We have synchronized all Log times to GMT in BPS Pro 9.1 since the Log times were being displayed in UNIX Server time. This was more for sanity sake, but I did come across a problem in testing. Either way all Log file times needed to synchronized to a standard time since all other times are in GMT for everything in BPS Pro.