I see your point, but in my experience you can ramp up some eg: Java developer real quick; and in a couple of months they can quickly start to become more productive than with Java.
There are alot of caveats here, and it highly depends on the teams, projects, maturity, quality of tools, and so on, but there are not alot of weird concepts in clojure that makes it that hard to understand (as a counterpoint to eg: rust borrow checking rules, or C++ templating, and so on).
The hard part with clojure is having just enough discipline to keep things in check.
There are alot of caveats here, and it highly depends on the teams, projects, maturity, quality of tools, and so on, but there are not alot of weird concepts in clojure that makes it that hard to understand (as a counterpoint to eg: rust borrow checking rules, or C++ templating, and so on).
The hard part with clojure is having just enough discipline to keep things in check.