Repository listeners on the user interface are having currently a problem that they also are informed of the OnlineStatus.CHECKING state. They should only be informed about the ONLINE and OFFLINE states. Thus listener interface needs a refactoring and all implementing classes then can have a much simpler way to handle CMR online status.
I wouldn't refactor it so that we don't have that information anymore. How about specifying on which events you want to be informed as a listener? Thus passing ONLINE + OFFLINE will exactly lead to what you proposed with the flexibility of listening on CHECKING if we need to.