Feature to see results of incomplete scan & restart from point of failure

Problem

The scans take up much memory and cpu resources (no complaints about that though), and can take a long time. So the user should be warned to expect reduced performance experience for their site visitors during a scan.

Suggestion

For this reason, it would be very handy to be able to schedule scanning for off peak.
It would also be handy to be able to suspend the scan, either manually or by schedule.
It might even be possible to let the user save settings for “preferred scan times”, so that when they do a scan in future, then there will be the option to select the “best times” (or run now).

The scans can fail

.
When the scans fail, all data appears to be lost, or made inaccessible.
As a work around, a page refresh in the browser may trigger the scan to continue, but this often starts at an earlier point to where the scan failed.

Suggestion

If a scan fails, then at least be able to see the results that were obtained before the failure.
If a scan fails, it would be handy to have the option to resume that scan (which may not be the next scan that is done after a failure) again. The starting point for the resumed scan, could then be established form the previously saved data from the failed scan.
In any case, allow the user to manually select which plugin, plugins, or “group” of plugins they would specifically like to scan.

Suggestion for automatic scan for several PHP versions

It would be handy for user who are several versions of PHP behind, to be able to scan compatibility with the several later versions of PHP, so they could select the best trade-off between compatibility and site function.
So allow the user to select more than one version of PHP to check, and then run the scan for all of them at once.