Accurate last modified date/time for fields without history tracking

Who would benefit?

Customers and partners implementing publication processes or users who need to backtrack why an entity got changed

What impact would it make?

Reduce the number of times an entity gets published and the ability to see the exact latest time a field got updated

How should it work?

Fields without history tracking get the same last modified date/time as the entity even though the field itself did not get updated.

Unlink the field's last modified date/time from the entity's last modified date/time.

When an entity gets updated (via UI, REST API or other processes), do not update the field's last modified date/time when the data itself did not change, or the field was not part of the list of fields to change.

Why is it needed?

A best practise from inriver is to limit the number of fields with history tracking enabled. But that removes the feature to exactly see when a field got updated the last time.