A TimeSource can manage multiple Clocks (from the design doc and the rclcpp implementation).

Currently all clocks attached to a TimeSource use the same property for use_sim_time, and the time for each clock gets set to whatever is received on the /clock topic. What is the anticipated use case for having multiple clocks managed by a single time source? (all clocks attached to a TimeSource seem to behave the same at the moment, but that may just be a "for now" thing).

Is the predicted end state that multiple nodes' clocks are managed by a single TimeSource, but each clock would be able to have its use of sim time enabled/disabled independently? (Currently the use of sim time for each node is configured independently because each node has its own time source).