This is all faith from me, but Valve does not always wait for massive community backlash to fix stuff. People like sigsegv have seen many bugs they submitted eventually fixed, and all they did was post video evidence and send emails.
While I have faith in Valve eventually fixing the thing, I really don't believe that they will change their update "schedule" for this. With no hints of any update in sight, we'd be looking at 4 months of unplayable spy assuming the update drops in early July, or 7 months if it eventually happens during Scream Fortress.
Also, the comp community is too small that even if we all started abusing this, we wouldn't make enough noise for Valve to consider us. You'd have to get pubbers on board, and they won't care since pubs are on sv_pure 1 anyway.
To me the options look like this
Situation 1 : We try to limit the spread as much as possible so that most players don't have to play against this, while hoping that Valve does something next update.
Situation 2 : We somehow rally a large enough portion of the community under our banner, make spy unplayable everywhere for at least half a year and we're still left hoping that Valve fixes it since it does not affect pub play so it's not really a priority.
I understand that it is frustrating to have to wait for Valve to fix their game for absurd amounts of times even 10 years after the launch, but seeing as the TF2 staff is made up of 2 and a half dev and a potted plant, I really don't think we can do anything to rush them by making spy utter garbage.
To me our most realistic options have to be built by us, either a plugin blocking that or a way to detect it for AC review, but I don't know a lot about the technical side of the game so I don't know how feasible that would be.