According to the MAVLink spec it should behave in the same way as is speced for loss of the remoteID heartbeat - which is to post remoteID malfunction in the LOCATION message status field.
There might be other requirements not in the MAVLink spec I guess.