Best way to handle interconnected climate entities?

[fading path]

I have eight climate entities: six ESPHome heat pump mini splits, and two Z-Wave thermostats controlling baseboard radiators. I can control all eight fine from HA. However, there are some interconnected relationships:

• All the mini splits MUST be set to heating or cooling, as they share an outdoor unit and the entire system is either heating-only or cooling-only. I cannot heat bedroom 3 whilst cooling bedroom 1.
• The baseboard radiators affect multiple rooms - e.g. the thermostat is in the main bedroom, but applies heat also to the kitchen, dining room, office, and living room
• The radiators and heat pumps should not operate simultaneously. If I request heat in the main bedroom, the mini split should be used UNLESS the outside temperature is below a user-defined threshhold, in which case the radiator should be preferred (this is a standard operating mode of the Mitsubishi Kumo Cloud system)

I've seen a few multi-device entities like Better Thermostat, but they seem hyper-focused on per-room TRV. I'd welcome suggestions on the best way to simplify my interactions with the system, ideally presenting only a single climate card per room.

[fervent spruce]

Honestly... This is quite complicated and there's no real way to do this easily. AFAIK, there's no off the shelf (or even out of HACS) solution that will do everything you want unless you go very generic like a template climate like this https://github.com/jcwillox/hass-template-climate
That would let you bake in automation controls to allow (e.g.) turning on the AC in one room to disable the radiator loop that also serves that room etc. But definitely not trivial.

[fading path]

hm. ok, i appreciate the pointer. I'd be mad if there was some magical solution I missed which I discovered after sinking hours into DIY templating