And if the cash box is empty every day, and the book-keeper drives a new Caddy and takes periodic trips to Vegas, we can be sure he is embezzling.
It seems to me quite simple to construct an algorithm to evade Regan's screen. Call it the "Engine Manager".
Relative Blunders: When running a blunder check, the software often finds "blunders" where the winner passes up, e.g., a +7.50 move and makes one netting "only" a +4.25 -- a relative blunder that makes no difference (assuming competent play subsequently).
It's a relatively rare position that has only one or two plausible moves. Quite often, there will be eight or nine moves differing by only 15 or 20 centipawns.
First cut at Rules for the Engine Manager:
(1) Never make the top or runner-up move in the list of the engine's candidates, unless necessary to avoid loss. Scan down the list until encountering a candidate 15 centipawns worse than the leading candidate.
(2) At some random interval, select a candidate 40 centipawns worse.
(3) At some random interval, offer a draw when you have a 50 centipawn edge.
(4) Always make Relative Blunders where possible.
(5) If a sacrifice requires over "x" ply (20?) to demonstrate its correctness, choose an alternative.
(6) Allow manual override. Assume the operator is high Expert or better with at least some notion of "computer moves" and how to avoid them. A clever, patient operator would throw a game every now and then to avoid meteoric rating jumps.
Now, a real GM could probably examine a game played according to such an algorithm and suspect chicanery, but the game should pass automatic cheat screening.