For my 2 cents, if you have the time, it would be interesting to see how the tool ends up.
That is, I wouldn't expect any particular adoption, and I would focus on what you need from the tool first and foremost w/ small and simple dev effort. This space is super complicated and people will have all sorts of contradictory needs (Andrew does a good job of setting realistic expectations). If something broadly useful comes out, nice. If it scratches your itch and entertains you OSS wise but no one picks it up... still ok, and maybe we learn something. Somewhere in the middle, there's a "boring" tool that helps for some simple/common cases, and can be ignored outside its scope. I'd be happy to learn about any of these outcomes.
On another front, if automating some simple TLA+ transformations/analysis is the name of the game, I have been working on a library-form version of TLC for a little while, and I could make it available for your use. It's a Scala library and loads the TLC codebase, so not exactly that Rust prototype (though don't assume you'd have to ship a .jar). On the flipside, the library links with full SANY, and can broadly interfere with TLC's function in all sorts of fun ways: hooking into module lookups, scanning the AST + module hierarchy, doing thread/restart-safe custom expression / state evaluation (not that you probably need that last one). Feel free to message directly if interested. It will ultimately be an OSS project on our lab's Github, I'm just slow / dealing with a related academic paper submission. No pressure to try it, just kinda related. This paragraph and the one above are orthogonal.
Best,
-Finn