pull down to refresh
If you are talking about scripted multisig, i.e. one that uses either OP_CHECKMULTISIG or a leafscript with OP_CHECKSIGADD: No, because the address is a representation of the output script, and the output script includes a definition of which three public keys form the quorum. Changing the quorum will therefore change the output script and a different output script will be represented by a different address.
If you are talking about a P2TR output encoding an output that under the hood can be spent with a 2-of-3 threshold signature (e.g. using FROST or ROAST): Yes, because you can use two private keys to create three new shards of which 2-of-3 are sufficient to produce a valid signature. This allows you to rekey your wallet without moving your funds.
This is a bit of UX question - in Zeus (and other apps) there is always some new thing, interaction or new concept that you have to introduce to users, give it a name and a label in the UI.
What is the right number of new concepts that single application can reasonably introduce? When is it too much? Do you have experience with users giving you feedback on complexity of the UI? Have you ever thought about the UX from this perspective?