Rust would have to exist between C and python.
Rust is a compiled language. Presumably, the first Rust compiler was written completely in C, with newer versions having progressively more Rust source.
Obviously, Rust, with it's run time checks, can't match the performance of C without those checks.
A friend of mine who did a lot of Ada programming told me that his project turned off array bounds checking because it was just too slow for their application to function. There is little difference between that and coding the app in C.
A co-worker told me that early C compilers put bounds checking (and other checks) in to the generated code. He and his classmates routinely disabled the checks, only turning them on to demonstrate their code passed the checks.
I see no compelling reason to switch to Rust. If having those run time checks "built in" is desirable enough, I think it would make more sense to re-introduce those checks to C compilers, (Yes, I know, Rust has other features "built in", but most, if not all, of those features are available in libraries with many years of use and testing. (They might even be used by Rust.))