Version control - Diff is very confusing for ReadyAPI projects?

In any "project" (ReadyAPI or other), people might make small changes to the "project" and save their changes to source control. In such cases, I'd expect a small and simple diff. When the project is purely code based (ex. Java, Python etc.), then the diff is actually small and easy to understand. But, when the project is in ReadyAPI, the diff often becomes complicated and there is a lot of noise.

If I change one small line in ReadyAPI, then many other things might also get changed to support my change (i.e. metadata). Hence, it gets harder to read and understand a diff. There are so many confusing xml tags that we have to sift through to get to the main changes, for example:

</con:config>
</con:testStep>
<con:properties>
<con:property>
<con:settings>

How do you do code/test reviews with ReadyAPI? How do you cut down the noise? There is only so much you can do with ignore files of your source control.

Keywords: Git, SVN, Mercurial, Perforce, DVCS, Version Control, Source Control, VCS, Diff, Code reviews, Peer reviews.

PS: If found a related post, but it does not answer my question.
https://community.smartbear.com/t5/API-Functional-Security-Testing/Tactics-to-Overcome-Git-Version-Control-Issues-in-ReadyAPI/m-p/188598