@vandacca, I want to thank you for making me aware of some of the limitations of Bluetooth. I was tied up most of the day but this evening I have taken a look at the Bluetooth protocol, with which I have had no previous development experience.
Here's what I understand: Bluetooth employs a master/slave hierarchy. One master can have multiple slaves at the same time but each slave can only have one master at any given moment. In our case, the Model X is the slave, and the phones are masters. Slaves have the opportunity to select three different levels of security: open, first connection request for that device, every connection request. In our case, the Model X uses the second security option, and is therefore "open" to all masters with which it has been successfully connected.
That said - the Bluetooth stack remembers these by the MAC address of the Bluetooth master trying to connect. That MAC address is saved in software, and therefore I do think it would be possible for Tesla to manage profiles by swapping out the "active" MAC based on the selected profile. I haven't dug deep enough, but I'm guessing there is a related mechanism when you use the slave controller (in the X) to select a device with which you're not already connected.
I'll say what I've said many times before, much to the dismay of some of my colleagues/coworkers. "It's just software - it's not that difficult."