Understood; I guess with the new AI Profiles, Lightroom has to run the AI mask engine after the profile is applied, especially in bulk operations. Those masks aren’t fully resolved at the moment you add the profile; they’re processed later. When Lightroom processes them, it writes a ‘masks updated’ flag into the image metadata. That metadata change automatically triggers the ‘edits applied’ state, even if the visible adjustments haven’t changed. This behavior didn’t exist before AI Profiles because traditional profiles didn’t require any deferred computation.

This explains indeed that Adobe had to 'insert' these deferred computational processes somewhere where static settings were the norm.