You should be asking the question in what way does OOP mutate state and what other programming paradigms don't? What described above is unique to the oop style.

In general when you write rust. Unless you love oop, in general the syntax isn't set up to promote you creating a graph of objects that mutate one another. Java promotes this style the most.

For rust the style the syntax promotes is movement of data through pipelines. The data can get manipulated as it moves through the pipeline.

For functional programming it's similar. You have pipelines, but nothing is being manipulated. Each segment of the pipe in this case takes an input and produces a new output without moving or changing anything.