Could you elaborate on how combining a garbage collector with composition of data types works as an optimization?
Is this distinctly different than GC with an inheritance object model?
Obviously there are cases where you need that indirection (e.g if you're swapping out pointers to different objects in that field) but there are plenty cases where you don't (this usage pattern is a big part of the reason why write barriers work okay for these languages). Also note that you don't need to use indirection if all you want to do is use/store a garbage collected pointer to the field's object elsewhere in your program; the .NET garbage collector already has the ability to deal with pointers within allocations. It's just that they've stuck to not discriminating between these within the language for simplicity (IIRC the .NET runtime can sort of use interior pointers to structs, but this isn't exposed in C#).
On top of this, a programmer's input to the optimization process rarely extends past "inline/don't inline this function". Compilers have to make optimizations that are either strictly better or base it on a wild guess of the time, instead of using profiling to either automatically or manually (i.e. overridden by humans after they test the code) invoke optimizations. Many compilers offer profile-guided optimization but few projects use it, and the JVM just uses it to smooth over some of the performance loss from lacking things like value types or refined generics. In languages that provide sufficiently low level operations you can sometimes get what you want by altering the code, but that doesn't always work.
I'm excited for us to stop using Moore's law as a crutch (which has stopped on desktop CPUs for a while now as far as performance if not price) and to look at things like improved tooling, improved languages, and hopefully even improved architectures. I find it hard to believe that "5nm transistors arranged into x86 processors running hand-optimized C code" is the epitome of feasible computing in our universe, and that's forgetting that most of our code isn't optimized anywhere near that much.