wp_fastest_cache_Preload blocks other cron jobs

I have site-visitor “virtual cron” disabled. I trigger cron jobs once per hour, through host tools.

When wp_fastest_cache_Preload is the first cron job in the list of cron jobs that will/should execute, the remaining cron jobs do not execute. In my scenario, this happens every other hour (8am, 10am, etc).

wp_fastest_cache_Preload is first in the list of cron jobs, when it has the oldest unexecuted scheduled time. Since it is scheduled to run every five minutes, it has the oldest unexecuted scheduled time every other hour. (This is because of the other cron jobs not executing when they should, so every other hour they will have the oldest unexecuted scheduled times.)

Then, because the other cron jobs were blocked after wp_fastest_cache_Preload ran (at 8am, 10am, etc), those other cron jobs then have the oldest unexecuted scheduled times, and they are first in the cron jobs list, every other hour (at 9am, 11am, etc). And so they execute, because they are in the cron jobs list “before” wp_fastest_cache_Preload.

Make sense? The point is: if the wp_fastest_cache_Preload appears in the list of cron jobs to run, at the next triggering of cron jobs, then the cron jobs that should run immediately after wp_fastest_cache_Preload will not execute.

wp_fastest_cache_Preload seems to terminate the overall cron operation, possibly related to sending the cron output email. I dunno — I don’t want to figure it out to fix it. Hoping that the developers will figure it out to fix it.