It appears to be expected behaviour that a metadata refresh initiated on a lagging secondary will be waiting for the replication to catch up to least the timestamp at which the refresh was triggered.

At this moment there is no way to infer from the messages produced by SH_REFR if a refresh was/is waiting for replication.

Can we please improve the logging detail in that regard?