Sorry about that sir I missed this! I can only speak for our team specifically about the why, although I imagine every team is always looking to do things in a way that is easier to maintain. Any team that has to process large amounts of data and/or has a somewhat complex schema for their data are looking into Rust. For right now it seems to be used mostly for infrastructure type dev work more so than calculations to risk or price derivatives. Code that is legacy in C/C++ or Java are prime candidates for this migration. While I am specifically in a fixed income derivatives team, I know it is being looked at by commodities, foreign exchange (FX), and equity teams as well with similar future concerns when it comes to their data.
For us we have lots of data that we need to slice through in json and xml formats from various external and internal sources that aren't from our own team for financial data. The current code that is in C or Java is extremely hard to maintain, if not outright just bad with memory leaks that require jobs to be restarted every other day type thing. While I would personally love to hire a couple skilled C guys to clean up these processes/jobs, the kids coming out of school just aren't trained to think like the C programmers of old. Even when I went to school in the early 2000s, we were taught Java and not C. The memory management and concurrency use cases they have in Rust with their ownership model make things substantially better once we get things to compile properly.
We also have the added excitement/pressure of needing a language that is interoperable with Python, as this is a language that is almost sure to come up somewhere in the development cycle for one of the layers. It is why we are eagerly awaiting Professor Duffy's book as well.
Happy to answer any specific questions if I can!