Having a "bug fix" team is an impossible venture. Anyone working in software will tell you that the best (sometimes the only) people to fix a bug is the original programmer. Bringing someone in from the outside, and saying "Fix this..." is akin to Stephen King to rewrite various sections of the Lord of the Rings -- it might work, but lord knows it wouldn't be pretty, and would likely cause more problems than it fixes (not a perfect analogy I know, but it's functional).

Similarly with any software, bugs are not isolated occurances - it's like the butterfly effect. A butterfly flaps its wings in Japan, and as a result a jet explodes in New York -- the principle is the same. Changing one thing often has unforeseen changes in other parts of the application. Then you run into the idea of too many people in the kitchen - you have bug-devs changing things, and it effecting patch/content devs, and then patch/content devs changing things which in turn cause more bugs ...

Again, not a perfect analogy but it works.