I am reworking the code that handles pause/resume around mover/CA backup running, so hopefully that will either fix the issue of resume not working, or if not at least give some insight as to why.
As to the history giving strange results can you look at the config/parity-check.log file on the flash drive (it is a human readable text file) to see what the last few entries show (and possible let me have a copy) so I can determine if the problem is something that has crept in around displaying the history, or if it is actually an issue recording it in that file (which it is should be obvious). If the latter I would appreciate a a copy of the parity.tuning.progress.save file from the plugins folder on the flash drive as that would have been used to generate the last history entry.