The request here is to always align the secondary nodes to have the configuration files as on the primary node (+ database) and not inspecting the timestamp.
This comes in two scenarios:
1. If the binarystore.xml was unchanged on the primary node (supposedly from version 5.2.1) and a newer binarystore.xml was unpacked and has a newer timestamp than the binarystore.xml on the primary node and database - it will not be synced over to the new secondary node.
2. Some customers are doing automations with settings on the secondary nodes causing the timestamps of the configuration files to be newer than the ones saves on the database (which are saved from the primary node):
One example case for this is a scenario where an automation samples the binarystore.xml and changes its modification date, later on, the customer do not understand why the binarystore.xml is not synced, causing their files to be ending up on the local file system instead of the desired (and configured) storage, as on the primary node.