Have you considered to use ordinary batchfiles?
Triggered continuously by windows scheduler,
starting an inspection-application (QV), which at the end produces a file if update is finished
if the file exists (or even inspect it) continue with batch-excution (qv.exe /r yourapplication.qvw)
if not - terminate and wait for the next trigger from scheduler.
note: applications initiated in a batch should have SET ERROMODE = 0, in order not to stop on errors.
You may construct similar also w/in QV (via EXECUTE), but personally trust more on batches.
What you mention is (almost) exactly what I have in place now and it works great. I use an oracle package and a few powershell scripts to manage 100+ reloads and publish events. I spawn concurrent reloads based on data readiness, available RAM/CPU and check the log files for errors.
The reason I'm trying to find a qv solution is that our qv developer team and application set is growing. Everything new has to come through me and any issues can only be resolved by me. I don't scale well :-) and will soon be a bottle neck/single point of failure. Not good for me or my team.
If the QV scheduler simply cannot do anything like this (hence the current process) then we have to come up with another plan.
I know we are not the only ones with this "data readiness" issue so I thought I'd kick it out to the forum.