That's exactly why our Data Engineering team is also looking at Rust, but we're looking at Go, too. I have a hunch that Rust is going to be a harder sell to the broader team given its learning curve and that most of the team don't already have a compiled language in their tool belt. I'm quite open to either, though, as they'd both make my pipelines go vroom.
Rust has the upper hand for incrementally replacing Python modules. With PyO3[0], you can seamlessly replace existing Python code with native extensions written in Rust.
If your use case is to replace entire tools, and your team isn't familiar with static languages, then Go is probably the better option. There's no denying that it's much easier to learn.