Nobody likes bug-fixing: not their bugs and of course not other people's bugs. You can see this clearly in open-source software (mainly because the communication channels such as Bugzilla, forums, mailing list are all open).
It is like writing documentation: programmers don't like to do it. However, fixing bugs is worse, because there is really no payoff in doing that: if you create a feature or write a program then you are doing something new... whereas when you fix a bunch of bugs, then it mens at the end you get a piece of software which is working the way it was supposed to work on the first place... so for any external observer (client, manager, user, etc) there was no value added.
Wouldn't it be reflected in a drop-off of calls to Support/CS?
Hunting for an elusive hard to fix bug might be very satisfying. You get to know the environment, you might have to construct custom tools to gather data for the debugging purposes and you obviously get the bragging rights if you succeed.
Most bugs are not that challenging though. A textbox is too small to display a value, shoveling of records from point A to point B loses some data fields, this kind of stuff. You basically know right from the start what kind of fix is required and the only challenge is finding the place in the (potentially messy) code where the fix needs to be applied.
What you subsequently described is a copyeditor's function on a book. Maybe such jobs need to be described as such to attract the people who really want to do them?
I'm partly speaking from experience here.