AFAIK this is impossible, at some point your binary needs to be loaded into memory. Unless it is being loaded into a secure region of memory, it isn't safe. May I suggest a more open and honest approach with a custom integrity protection system, like storing file hashes. Nothing is going to stop a dedicated reverse engineer, and everything is vulnerable whether you like it or not. Have you thought of solutions that don't involve actively hiding the binary from users and instead take reasonable steps to protect stored information.
Maybe rethink your trust model to put the user at the center of it.
[quote='791099022, CMDdev, /thread/757126?answerId=791099022#791099022, /profile/CMDdev']
even preventing the binary itself from being read
[/quote]
