You cannot stop a map from being rigged. It is just that simple. Just as simple, in fact, as you cannot protect a map. There is no native map encryption in starcraft, only attempts by programmers to add things into the map code (or remove, or change things) that makes it still readable by a starcraft error bypass and unreadable by staredit or any map editor.
The problem is, if anyone knows the structure of a CHK file, they can simply extract the CHK and determine the differences. That way, they can reverse the differences and have an unprotected map. In fact, there are many guides out there on how to unprotect the most common protections (including the newest version of PROEdit).
Although it is unlikely that any noob who can't even win your map would be able to extract the CHK and hex edit it back to normal, you might be surprised.
So, in conclusion, you cannot make an unriggable map. If somebody is stupid and sucks enough, they will unrig your map. The only way to stop it is to use a combination of protection methods, and add some of your own. You cannot stop the hackers, only delay them.
Although, it wouldn't help to beg for them to stop in the trigger code

[right][snapback]137627[/snapback][/right]
That is true. But as of right now the publicized steps to unprotect ProEdit v1.4.1 are so long I highly doubt anyone would do it.
I think they should just quit.