If you, for example, hold your voxel level data in a big array, that means copying that data every time the level is modified.
Its not react style its literally the core of how react works(immutablity). To rerender a component you need the new state to point towards a new reference to an object/array (hence the copying data to a new array) because JS compares objects/arrays through reference and not value. Not exactly react's fault but how JS works.
You are more likely to a struct of arrays than an array of structs/objects as well. Very handy in C but also JS.
I suppose you can use a sliding window object (or “fly” object) that pretends to be the object when the data is really split across various arrays, just don’t actually loop over them. ;) I bet someone has done a library for something this way and used proxies.