You could write a routine to find them, but there is no way to distinguish between legitimate user changed values and values that have been unintentionally stomped or failed to propagate.
Work on a text format for uassets is ongoing. You can enable the experimental support (TextAssetFormatSupport in experimental settings) and then right click on a blueprint and select export to text asset (don’t recall the exact phrasing). Your .uasset will become a .utextasset and you’ll be able to open it in notepad or whatever text editor you use. You’ll see significant amounts of binary data that has simply been converted to base64, but other parts of your blueprint will be quite comprehensible.
We hope to begin using text assets internally in production (rather than in engine test environments) very soon. Just to emphasize: at this time I would not recommend exporting all your blueprints to text assets and working that way - you would be the first person in the world to do so and would likely find some pretty rough bugs! It is a useful tool to audit the editor, though!