Hi Yoyogi, Funkenstein,
Opening blueprints to check content marking blueprints dirty was a bug and has now been fixed - there was no reason opening a blueprint without modification should trigger anything to be dirtied.
It’s true blueprints don’t interact with source control in the same way native code does and we are aware of the issues with source control. Some work has recently been completed to try and minimize how aggressively dependencies are dirtied and was committed in changelist 2266069 on the 28th August. I don’t expect that this will completely eradicate the issues, but other efforts are being made to try and improve workflow with source control and blueprints such as the merge tool.
If you find once you have these changes that you still see instances you are sure are errant with blueprints being dirtied please report the issues and we will look into them.
Hope that helps
Cheers!
Ben.