The brief non-permanent bluetooth profile breakage is also triggered by opening about:support in Firefox or "Help > Troubleshooting Information" in Thunderbird, both of which I assume enumerate/probe audio devices. So it seems like this is indeed related to some applications probing audio devices, maybe by even briefly opening them, and that possibly automatically changing to a low quality audio profile if it involves a microphone. Which seems like without user confirmation, it probably shouldn't do. Seems like this might be a pipewire issue then?