No, this would not identify which field(s) a change occurred in. I think that what I've suggested, might be a possible solution to the initial requirements, but does not address these new requirements.
Which means, the first step, and what you've now presented as the next step, probably won't work together.
This probably means that you'll probably need to go back to the drawing board again, and rethink the strategy. You would probably need to do different things when only one field is changed vs more than one, vs new record, which I don't think your initial code/requirements included either.