Could a (single) patch point be made external to appear like a hardware input?

Between the JP release and the recent collaboration comments, this idea came to mind, but I wanted to throw it out for info gathering. Some sites/companies already have free services for "Netmeeting-style" conferences, from web-based (WebEx), to client-based (like TeamSpeak3).
 
I am more familiar with TeamSpeak 3, so will use this as an example. TeamSpeak 3 is free, and works well allowing for real-time connections of audio in a "conference" format, which would work well for easy collaboration. I recall trying to use LoopBe in the past, but didn't like it (and cannot remember why now); and this client alone would allow for collaboration *if* it could see "SONAR" as one of its hardware input.
 
At this point, this is more curiosity to determine if such is possible, then I can submit as a Feature Request.
 
My thought is pretty simplistic:

1. Allow SONAR to use a single patch point (e.g., off the Master Buss) that would be seen externally as "hardware."
2. User could use client of choice to enable this input.
3. Collaborate via that client.
4. "Icing on the cake" would be if SONAR could also appear as a single hardware output, to record (muted of course) this session as it occurred (this would be lo-fi, but would allow quick guide track construction). However, if truly done in a collaborative environment, each person could/should record their own work. This particular bullet also throws in some "monitoring" issues, because it could achieve a feedback loop or inability to hear the session.

Any thoughts on this? Is such a thing feasible? The point of this is "ease of use" so that users do not need to jump through burning hoops of fire to collaborate.