I would hire the guy who notices the CAS in the protocol rather than the one who forks memcached, creating a maintenance burden, and potentially introducing safety or liveness issues (although memcached is somewhat simple, most databases are not, especially distributed ones, bring your TLA+).

And memcached isn't going to pull your changes either, because they want a simple protocol. It's not a CRDT-oriented project.