Kawa predates Clojure by a decade. (Kawa work started 1996; Clojure's initial release was 2007.) Also, Clojure isn't really focused on high performance, while that has always been a priority for Kawa, which generates bytecode similar to Java, especially if you include suitable type annotations. (It is likely Clojure have have improved in this respect - they have a lot more people working on it.)

Agreed, "Java" was an oversimplification. It's actually JVM bytecode. It's still strange in my book to use an object soup runtime for something (Lisp/Scheme) that feels closer to functional languages to me.

Clojure is a different case, because when you already are on the JVM anyway, then Clojure is still infinitely better than no Lisp at all. It's not the same as putting the JVM somewhere where it wasn't before and where it's not actually needed.

RMS itself being a diehard Scheme and Elisp user said that he found Java elegant over C. This was OFC long before Go and when C++ was king in the 90's.

On Java itself, when CLOS, a dog-ancient system for Common Lisp it's enough to support the Java class/method/object system by itself tells a lot on how great CL can be, even with SBCL which is the top tier free (as in freedom) interpreter/compiler out there.

On performance, well, who knows; remember that PyPy itself back in the day was written in Python itself and it ran things much faster than the vanilla Python interpreter.