My understanding is that Jank is built to provide tight integration with C++, and does not aim to be a drop in replacement for Clojure. Jolt provides FFI for native ecosystem access, and aims to be a superset of JVM Clojure leveraging platform specific features like TCO and providing fibers built on top of continuations. It currently runs many existing Clojure libraries out of the box.
I am the author of jank. Saying that jank "does not aim to be a drop in replacement for Clojure" may send the message that jank is not a full Clojure dialect. This is unclear at best. jank is a native Clojure dialect with seamless C and C++ interop and a strong native ecosystem story, including native project and dependency management.
I believe what you're trying to say there, with "drop in replacement", is that jolt emulates common Java interop forms in Clojure JVM such that code written for Clojure JVM doesn't need to be ported to run on jolt. This a compelling feature which other dialects are tackling as well.
What I would mention as a key difference between jank and jolt, aside from the C++ story and native project management story, is that jolt is very much AI coded and jank is not. jolt doesn't disclose this on its website or Github readme, but it's something which clearly matters to a lot of people.