Hence my analogy upholds.
Your analogy is better suited to ELF obfuscation. You can drive the car, but you can't figure out how it drives.
Its completely different area, mostly a con than a pro. But imagine situation where you need your server binaries to work, yet be useless for cracker to disassemble/analyse if he cracks your machine. For example, banking field.
Hence the true protection is the LICENSE, which legally prohibits misusing the double-edged tools. This is why GPL is simply a brilliant thing, and BSD is unsuitable in this context.
The complete data test would be field testing, so lets wait for actual implementation to see outcome.
The idea is to execute only the code which has not deviated.
Package CRC idea is to deliver the package which has not deviated. Its comparable to archive CRC.
Overall it nicely adds up, you get checksums in git, checksums on package, authentication on download and authentication when binary is executed.