I understand the frustration with users who may be blindly IDing with the CV. However, I don’t think allowing ad hoc disabling of a key feature of the platform on a user-by-user basis is a good solution. This is likely to create lots of confusion (many users wondering if CV is broken, etc.). The CV is also used as autocomplete by many high-volume, expert IDers. Disabling the CV for some observations is likely to reduce their efficiency. As such, I don’t think the benefits would outweigh the costs.
The best solution is probably to try to educate the users as others have suggested and then, if the problem is egregious and persists, to contact staff.