It also swiss-cheese's my schedule, because instead of setting aside dedicated time for pair programming and for information exchanges or meetings, like you would think you should do in a professional workplace, those events are now thrust upon me even when I might be trying to finish some other work or I might have to urgently focus on something else.
The entire premise that continuous real-time audio is somehow synonymous with idea-sharing or collaboration is just insane.
Sincere collaboration is respectful of each individual's time and planned work schedule, as well as individual preferences for quiet, privacy, etc. Sincere collaboration can be asynchronous, textual, visual, or auditory (or a mix), can be remote-friendly, etc.
What you describe as "forced information exchange between people" is appropriate maybe for a trading floor or mission control, but the attempt to stylize a bullpen of software engineers in the same way is disaster, and at best it is superficial collaboration.
It just has to be planned, put in a calendar item I can plan ahead for. If it’s constant pairing or if it’s ad hoc pairing that is thrown, unplanned, into my schedule, then it’s always a bad idea and makes both people worse off.
You also have to ensure the noise generated by pair programming doesn’t affect other workers who happen to sit nearby. They don’t benefit from my pair programming, and shouldn’t be forced to reduce their own productivity by putting on headphones, working from home, trying to find a conference room, etc. just because of my pairing session.
It's not comfortable, it's not necessarily conducive to YOUR methods - but you put enough interesting people in the same space and you're bound to jumpstart something. Maybe an HR incident, but something.