We can have an editable grid / store use case where a user can edit fields within the record, but for whatever reason we are also programmatically calculating and mutating values (metadata of some kind) that we want to be effectively ignored for the purposes of evaluating StoreRecord.isDirty.
Currently we have to re-implement a custom dirty check and skip using the store built-ins.
Note that this might be an enhancement to consider while continuing to look at. #4011 as both relate to dirty checks at the record + field level.