An engineer designing a product can certainly run it through a simulation that accurately predicts elastic and plastic deformation as well as fracture and other failure modes.
Simple mass-spring systems (like this) have issues with really stiff springs and high masses causing unrealistic responses even with a low time step but you can use approaches like XPBD which are stable. Changing the configuration of constraints is what causes the shape change.
Most vehicle sims get really far with just using a rigid-body system and modelling the damage another way. It’s much computationally cheaper, much cheaper in terms of time to setup a vehicle and lets you maintain high fidelity in the driving model which is the bit most players care about.
It's amazing to think about all the objects in the universe which collide, always according to the laws of physics, not requiring any cost/resource/energy to such computing loads, and reliably without any uncaught exceptions.
It is highly distributed, in that every atom in the universe is performing this "calculation", all the time. That is literally an ungodly amount of energy. As for uncaught exceptions, they are also performing "only" this calculation, not much room for exceptions there. But let's not talk about quantum tunneling and other weird things that go on in the even lower level VM ;)
An example: https://youtu.be/z12UdMbELdc
The whole Siggraph channel is quite cool. It's just demo videos.
It's about typical for modern physics engines.
Totally rigid body physics is reasonably well solved by now. It suffers from the "boink" problem; in impulse-constraint systems, there are instantaneous changes in velocity on collisions. This looks OK for small objects and terrible for large ones. This is the main reason game simulations usually look wrong.
If you make everything soft, that works OK. But everything looks like Jell-O, as some early Pixar devs wrote. That's a soft-body system.
What's hard is doing things which have just a little elasticity. Which is most real-world materials. That's because you have to simulate what's happening on very short time scales, much shorter than a visual frame time. This is possible, but the compute load suddenly jumps by orders of magnitude during some collisions. That's hard for real-time systems. Also, you start to need double precision. If you don't need real time, as for film work, it's not too bad. Integration of stiff systems of differential equations is Not Fun. I used to do that stuff.
Note, in the video, how soft the suspensions are.