Now, financial software may get away with those because they don't really have a choice: they are a narrow field, with a critical need for correctness.
Conversely, you could say that most projects get away with ignorance. They use sub-optimal languages, for the very short term benefit of not training people.
Haskell is beautiful because smart people find it to be a really good way to express their problems and solutions. Haskell is the way their thinking comes out. So if you're in that 3% you probably know and possibly even use Haskell already because you have that sort of train of thought. If you're in the remaining 97%, you could only do much less or barely nothing at all until you had had a long series of "aha!"s, not often even related to Haskell itself.
Instead of language training, effectively a mindset-changing smartness training is what would have to come first.
At $WORK I used to show some cool stuff in another language and tell my coworkers it is built-in in Haskell (the concurrency stuff is what interested them.) I hope some of them will have a look at it in their spare time.
The core Haskell module itself solved a specific problem beautifully, but it all got very messy outside the confines of the pure and pretty functional world.
Especially the Lisp community seems to be almost completely American to me (in Europe), with Racket in Boston, SBCL from CMU, and Clojure, too. What's going on in Lisp development in Europe?
Manager: WTF are you doing?
Employee: Making money
Manager: Fine, carry on
So there are a ton of exotic languages kicking around (and even banks where some ubergeek has gone off and created an entirely in-house language, and then implemented some key system in it).And not just programming languages either...