I definitely think POSCON is on to something when they (a) are building an infrastructure which allows pilots to receive positive or negative feedback just like controllers do, and (b) empower controllers to take immediate action when pilots are disrupting the frequency and/or the flow.

Making those actions subject to review, and to discipline controllers who abuse them -- and making the note that the pilot receives when it happens constructive, encouraging them to fix the issue and try again next time -- those are the challenges.  And they're big ones, which is probably why VATSIM leadership has balked at moving in that kind of direction.

Perhaps VATUSA or VATSIM HQ can build something similar to the real-world NASA Aviation Safety Reporting System, in which:

• Any participating member (pilot, controller, observer) can submit a report.
• Incident reports are made public but personal identifying information (PII) is redacted.
  
• Constructive feedback is provided to the offending pilot so they can become aware of their mistakes, when often times there is not enough time for the controller to explain everything in the moment online.
• Self-reporting grants the offending pilot immunity (at least for the first violation) from certain CoC/CoR enforcement actions.
  

As a long-term goal, statistics of the most common deviations at each facility can also be published, and facilities can address these specific issues.