Different poster, but I have an opinion.
I think that if you're going to do React/Redux, your life would be easier in Elm.
I'm a full time Clojure/Clojurescript dev and from my perspective, the main thing Elm is lacking is Protocols (in Clojure/Swift, Traits in Rust). I know Evan has been pushing back on it because it adds complexity to learning the language and you can get by without them, but I miss them. I could quibble about other things but there's nothing I strongly dislike. From an adoption perspective, I think a focus on tooling would help a lot. There was a talk at elm-conf where a refactoring suite was written as a chat bot. Ditching the chat bot part and building a language server [1] would make it much easier to pitch the language.
[1] https://github.com/Microsoft/language-server-protocol
For a non-web developer looking to transition into web dev, the main weakness of Elm is that the community is small so you basically have to build your components yourself. This tends to be challenging for experienced programmers coming from other languages because CSS has no abstractive power at all and the traditional layout techniques are incredibly unintuitive. You'll probably have the most success using flexbox everywhere. The community is friendly and I think Evan does a pretty good job leading it. I've pushed a number of younger developers at js meetups to pick it up and they've reported back with positive impressions. Of the compile to js langauges I know, I'd pick Elm as the most likely to succeed.
Overall, I like Elm and am happy with it's progress. I don't think it's ready for unqualified adoption, as you'll be doing a lot of library building you wouldn't need in more mature ecosystems and I'm not completely confident it's on the path to great success. I wouldn't push the language in a workplace at this point. By comparison, I would push Rust. You're in largely the same position in both languages in terms of writing libraries but I think Rust has hit critical mass.