You misunderstood my argument.

The point is, there are some domains (data-oriented programming) where Rust actively resists the kind of work you need to do to solve the problem in an optimal way, and it makes sense to use a language built around the type of memory management required.

There's no point in using Rust when 90% of your work is deactivating the benefits Rust provides and working around its default behavior.