I'm generally a fan of serious attempts to make alternate implementations of Bitcoin. I'm not sure that this counts as a serious attempt (is he really trying to do his own cryptography?) Also, I don't really think it makes sense to try to "freeze" the implementation of Bitcoin. If bugs are discovered in any of the code this project produces or its dependencies, surely they will be addressed -- at which point the box is open and we're back to a constantly evolving project (like all software?).
The two contributors on the github are listed as Seth Atwood and Claude.
Anyhow, here is how the project describes itself:
Bitcoin Echo takes a different approach. We implement the Bitcoin protocol once, correctly, and then stop. The result is not a living project with contributors and releases and roadmaps. It is an artifact—a crystallized expression of Satoshi's protocol that can be compiled and run decades from now by engineers who have never heard of us.
Where other implementations evolve, Bitcoin Echo ossifies. The system separates consensus-critical logic from platform-specific code, embeds all cryptographic primitives directly, eliminates external dependencies, and produces a codebase simple enough to be understood completely by a single competent programmer.
Projects like libbitcoinkernal (#1266973) seem like a better approach.