Each Material Definition wants to be able to show its material, whether via the rendering material or through the linework and hatch assignments for non-rendered views, in its own unique way. To be able to do that, they cannot all use the drawing default display settings, or they would all be the same.
Perhaps a little history will make the need for style-level overrides in Material Definitions more understandable. In the early days of what eventually was called AutoCAD Architecture, there were no Material Definitions. The way an object component displayed was governed by its display settings. For multi-component object types like Walls, in order for Component 1 in a brick Wall to "look like" brick while Component 1 in a gypsum wallboard Wall looked like gypsum wallboard, style-level display overrides had to be placed on each Wall Style. That works, but the problem is that once you apply a style-level override on a display representation, all of the settings become divorced from the drawing default settings, even those that are not overridden. Any changes to the drawing default settings would have to be made to all of the overrides as well. Also, you had to be rigorous in setting up the overrides, to have all brick components look the same, and all gypsum wallboard components look the same, etc.
Material Definitions allowed for once central definition of how a particular material should appear to be created, and then applied to all of the components of that material, in all of the object styles in which that material occurs, without having to add overrides to each object style. Any drawing default changes to components that are not based on a material will be seen in all styles. If a change to the way a particular material should appear (perhaps the hatch on brick should be spaced a little further apart to improve legibility), it only needs to be changed in the Material Definition, and it will affect all places where the Material Definition is used. It also allowed for rendering materials to assigned to AEC object components.
David Koch
AutoCAD Architecture and Revit User
Blog | LinkedIn
