Yeah, this all points to what I think we have requested in the past. We want to specifically designate which device to associate with a particular sensor input. TR will freely substitute if/when dropouts happen, and the users has no idea that a swap or issue has occurred.
It leads to confusion since we never really “know” what data is coming from when we have multiple devices paired. Zwift and other apps allow specific designation of a sensor to a piece of data, and that is a better approach, IMO.