You could use QVD generator scripts, as in load scripts that save their output table[s] to QVD file[s] held in the file system.
Then for your dashboard qvf just have a simple load script that simply does optimized loads of the required QVD's. It will reload all the tables, but such a load script will run very fast.
For the table that needs reloading frequently you can reload its QV file frequently, and for the others reload them less frequently.
Thanks, Bill. The app is indeed using QVDs, and I have temporarily replaced the loading of this particular table with script that loads it fresh from the database (so that I can see the changes without recreating any QVDs). So I am sort of doing as you have suggested; the loading of the table from the DB only takes a second or two, but loading everything else from the QVDs takes about 30 seconds, which is what I was trying to cut down on. For the amount of data involved, the 30 seconds is quite fast, so I guess I can live with it.