Well, it is quite simple: As long as the klippy process on the host is running and answering requests from the MCUs the MCUs continue to function as they should.
If the host process stops responding in a predictable manner then errors like Timer too close or Missed scheduling of next digital out event are raised.
So, the case, where the host is not correctly responding is covered, but this does not seem to fit your edge case. Apparently the host process continues to run and thus also keeps the MCUs alive but other parts of the host system are no longer working correctly.
This seems quite unusual and, for me, the report and its validity are still not clear.