I’ve had this bug on the radar for so long I actually just dropped everything… 
Managed to reproduce fairly well, and added a small in-memory cache in front of the db which seemed to solve the issue (at least when it occurs from this situation - we have actually seen this before the supervisor starting saving the last reported timestamp).
Added the code to a PR here: https://github.com/balena-io/balena-supervisor/pull/988