<.inputs_for /> approach at odds with the new field-based change tracking?

Recently I have realized that when it comes to form data nesting, the approach suggested in the LV docs essentially nullifies the advantages of the new (optimized) field-based LV form binding as it requires using an (untracked) variable for the nested form data.

To be sure of this I refactored a form by separating some of the fields (the front-end related form fields from the domain related fields) and I made a parent-child form data composition using embedded schemas. Expectedly, the diffs sent to the client side grew up by a factor of 7.

Does anyone know if there are plans to rectify this issue in a not too distant future?