There are methods to extract and set such information:
View.GetCategoryOverrides
View.GetElementOverrides
--> OverrideGraphicsSettings.Get...{Various}
--> OverrideGraphicsSettings.Set...{Various}
You are then working with ElementIds, Colours etc. all of which can be represented in text. The CSV part you have to implement yourself.
Workflow wise I'd say the CSV part is not necessary:
Element Overrides are specific to one view in one document. If you want to transfer them from one view to another in the same document then you can do this in the API without creating external files.
With Category Overrides this could be useful to transmit between models but you can use view templates for this. You are only changing what is already represented in the visibility graphics i.e. overriding project level object styles per view.
I have though thought about this in the past for other reasons i.e. it is annoying when you drag copy a filled region on a view and it changes colour because someone didn't want to create a new filled region type with a different colour.
