I'm sorry if I came across as an arrogant open source bigot. I didn't mean to.
What I generally try to do when I find open source software doesn't do what I want is make the changes I want, compile and run that, and now it does what I want. Sometimes I send a patch to someone on the project team, or post it on a forum, and I have no freakin' idea if it ever gets acted upon. I've never felt the need to do this with Audacity, I'm generally content with it's idiosyncrasies, I'm referring to open source in general. I'm not completely blowing smoke out my ass, I actually have done this with other code including linux kernel driver modules, server code, stuff like that, just not audacity.
My first point is that generally this software (Audacity, The Gimp) has everything we need. If I can't see it, probably it's incorporated in a very clever way that I don't understand yet. Rather than ask the developers to dumb it down, perhaps I need to educate myself. In this case, I think splitting tracks and manipulating them as pieces is the beginning of a powerful concept, that is useful in general. Swapping tracks is one small use for that.
My second point is that open source projects makes progress when someone sees a need and codes a solution. In this case, if I can do something in 3 clicks, (split, move up, make stereo track) I personally don't think it's worth a lot of effort to make it "simpler", but everyone is entitled to their own opinion, and if you share your opinion and your code, it might be used. In this case it would probably be a nyquist plugin, which I suspect is much easier to get adopted than a core code change.