These messages are thrown by Joomla!'s JInstaller. JInstaller behaves as a black box. Once you get this error message it is impossible to know if the problem was a wrong/missing Download ID, failed download, unwritable tmp directory, extraction issue, a bad package (the developer did forget to add the XML manifest), a Joomla! bug, an installation failure due to uncommon permissions or something else I have not yet seen happening on a site. Therefore, it is impossible to do what you suggest without polling AkeebaBackup.com for the validity of your download ID. And then, scaling issues begin.
If you have thousands of site polling AkeebaBackup.com every time they check for the existence of a new version or whenever the Live Update page is asked, within a matter of hours there will be no AkeebaBackup.com; this kind of traffic will effectively be akin to a DDoS attack and bring the server down. I know because that's what I did in April 2011 with Akeeba Backup 3.3.a2. The site was down in 2 hours, the host had to reboot the server and I had to redirect all requests to update information to a 403 error and, subsequently, to a CDN. That was the only way I could handle the traffic surge
So, no, this ain't happening.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!