I doubt it since chkservd simply sends the commands to the port and by definition that command will cause problems. Do you have some specific requirement to use it? It's a rather obscure way to prevent spam. You could remove the exim checking from chkservd.
Obscure, but perfectly within the specs. We've considering removing the check, but I haven't decided yet. For now I'm blocking port 25/26 for manually confirmed spammers/abusers's IPs and that works well.
I theory that option is a very good idea. In practice, there are some MTA's that ignore that RFC requirement, so you do run the risk losing legitimate email.