Context

I'd like my covers to follow different automation rules depending on whether I'm at home or away. I already have a Home Assistant input (e.g. an input_boolean or a person/zone-based binary sensor) that tells me which mode is currently active: present or absent.

For example:

• When present: standard solar logic, sunset at 25%, etc.
• When absent: more aggressive closing for security/energy savings, different default position, no motion-based behavior, etc.

Approach I'm considering

My idea is to create two separate ACP config entries targeting the same physical covers:

• Entry A — "Covers (present mode)" → with my normal configuration
• Entry B — "Covers (absent mode)" → with the absence-oriented configuration

Then, I would toggle their respective integration switches based on my presence input:

• switch.stores_integration_enabled → ON when present, OFF when absent
• switch.mode_absent_stores_integration_enabled → OFF when present, ON when absent

(Switched via a simple Home Assistant automation listening to my presence input.)

Question

Is this the recommended approach? Specifically:

1. Is it safe/supported to have two ACP entries managing the same physical covers, as long as only one is enabled at a time?
2. Are there risks of conflicts (manual override detection, command races, proxy cover state, etc.) when toggling the integration switch on/off, even with the other entry disabled?
3. Is there a more idiomatic way to achieve "two profiles on the same covers" within a single ACP entry — for example via custom positions, a force_override sensor, or some other mechanism I might have missed?

Thanks for any guidance!