I have multiple Fable apps in production - one of which for 2+ years. They are among the most stable apps I have published, and they are a real joy to maintain.
I too had initial concerns about adding Fable as a dependency, but it has been rock solid and has proven to be a great decision. The safety and clarity it provides by allowing you to use F# type system is a vast improvement over JS.
Many of the React libraries that I use already have bindings, and of the ones that didn't, I can usually create my own minimal bindings within a few hours. The community is also very helpful in this regard and are generally eager to assist.
With that said, if you want to go hog wild with incorporating every new React library out there, then this could start to feel like a hinderance if a library doesn't already have bindings.
But for me, the advantages of being able to use F# on the front and back end outweigh the inconvenience of occasionally having to create my own bindings. Plus it's fun (IMO) to contribute bindings back for the rest of the community to use.
It may also be worth noting that I look forward to waking up in the morning when working on an F# project!