Let's say you have your full setup on any slot rocking it (let's say huge modifications like xposed & maybe others (twrp, magisk/supersu, custom kernel, etc) on slot A) and suddently an OTA comes and flashes new full stock rom version on slot B and tries to run it succesfully on next reboot. And suddently after the reboot you find yourself on the updated new stock version on slot B without xposed (and without twrp&others too) in a clean instalation.
Now in this scenario..
a) slot A (which should have the xposed system you were rocking before the OTA and the succesfull slot change) is untouched or it is ruined with a copy from slot B after the succesfull boot??
b) if slot A survived untouched, can you just do a "fastboot --set-active=a" command and just reboot into the xposed system like before the OTA, or this doesnt work after the OTA and is ruined in some way?
c) if b) works (it should right.. right?), will the system try do download the OTA again asap you boot the old version on the slot A?
d) there's any way to block the Update Engine from updating, for example to wait till xposed is adapted for new version. For us Xposed users, waiting till new xposed version comes is a mantra that we have to do, and if we can't block OTAs or just undo what the Update Engine does... we're screwed?
Anyone on this scenario? I'm considering getting an A/B phone but this thing looks like a headache for anyone who likes to flash stuff and specially xposed.. since everything else you can reflash it on the new version mostly in a matter of hours/few days, xposed takes months to adapt.
I'd be glad if any Pixel xposed user could shed light onto those questions.