If spam protection is built into whichever client you use, it would simply be a matter of setting it to the proper value. And as long as you are true to yourself, you need not worry about botting. (Unless of course, if you don't want the temptation to be in front of you)

In which case, it's quite alright.
the 20 limit spam protection is old old old code, back from a much earlier, mystical time. Back then, we didn't have fancy shmancy trigger clients, so the code served a few goals:
1) old keyboards sticking, it happened, and it was sometimes nice to be able to get kicked off when you had the enter key stuck or something. (or the kill whatever command going off a thousand times) Closing off the program worked too, assuming you were in a windowed type of operating system.
2) silly 12 year olds who liked to logon and spam alot, you'd get the 20 spams, then they get booted, and you get a reprieve for about 2 minutes before it started up again

Or pray for divine intervention to appear
So realistically, the coder wouldn't have a trouble with removing it, but it's been with the mud so long, it's almost like cutting off a toe or something

albeit, a somewhat useless toe.. maybe like a 6th toe... sniff
Happy MUDing!