Cache preload feature request for w3 total cache

I have been comparing user experience on two identical test sites.
The site design is very light on css image quantity and file size.
It has only 10 pages/posts.
One uses wp-super-cache and wp-minify.
The other uses w3-total-cache.

With a primed browser cache, and an empty server supercache(or pgcache) both have very fast page load times of 0.8 sec. – 0.9 sec. for a single get request (200 OK) for a page (about-us page).
With the page cached in the supercache or pgcache the same single get request (200 OK) for a page (about-us page) loads in 0.2 sec. – 0.3 sec.

When I turned preload on in both sites I noticed a few peculiar things.
1). wp-super-cache pages and posts were always present in the supercache and loaded in 0.2-0.3 sec, but categorys and archives were never preloaded into the supercache.
Reason: wp-super-cache deletes the supercached version, then calls the url to generate a new version, but does this by calling postID.

2). w3-total-cache preloaded all pages and posts from the sitemap.xml, but always had some (10-20%) of pages/posts missing from pgcache at any one time.
Reason: w3-total-cache seems to rely on the garbage collection routine to delete the pgcache version then has to wait for the next cron run before the prime() function generates a new cached version.

I think all three of these plugins are just great. My preference however is towards w3-total-cache because it is so comprehensive in the methods available to speed up page load and reduce server load.
If it preloaded by deleting old pgcache file then w3_http_get to that url, sleep(x) then loop, then 100% of sitemap urls would be in pgcache 100% of the time with regulated freshness.
W3 total cache would move from superb to PERFECT in my estimation.