That's not so simple. By introducing this class it become public api. Anyone could override it. Modules could expect it exists and use it... It's not much likely, but it could happen. By removing / renaming this class, we would create backwards incompatibility. And that's very much against he tb policy.
I personally believe that, in this case, the functionality should be removed from core and moved to module. But if we decide to go this route, it needs to be done properly and safely. So the change won't take down anyone's server. You know, not the ps17 way.