Keep project update status in sync

Currently, the project update status may be collected for each remote site by the update module which is optional and the sequence on how often that happens is configurable. Onn the other hand, DRD collects the status itself for all monitored sites at once. It is not only likely but for sure that those two statuses are going to go out of sync. In addition to that, the remote status report (requirements) determine the status for the health section which is then displayed on DRD and that may be different from the project status list as well.

So, how can we resolve that:

Approach 1: force to disable the update module remotely and add project status to the status report by DRD

Approach 2: live with what the user decides to do with the update module remotely but overwrite the status in DRD and write that back to the remote sites

The first approach is much easier to implement but enforces some configuration on remote sites which hasn't been DRD's policy so far. The second approach is more complicated, follows the policy to not caring about remote configuration but it will write back stuff to remote sites which hasn't happened in the past either.

However, we have to bring the update status in sync. Otherwise we are going to confuse people. Is there a third approach? Or which of the two is the better one?