I don't know what all RO modifies, but the iron-ore item graphics are a little more than a single path string:
"iron-ore":
{
"type": "item",
"name": "iron-ore",
"icon": "__RealisticOres__/graphics/icons/iron-ore.png",
"pictures":
[
{
"size": 64,
"filename": "__RealisticOres__/graphics/icons/iron-ore.png",
"scale": 0.5,
"mipmap_count": 4
},
{
"size": 64,
"filename": "__RealisticOres__/graphics/icons/iron-ore-1.png",
"scale": 0.5,
"mipmap_count": 4
},
{
"size": 64,
"filename": "__RealisticOres__/graphics/icons/iron-ore-2.png",
"scale": 0.5,
"mipmap_count": 4
},
{
"size": 64,
"filename": "__RealisticOres__/graphics/icons/iron-ore-3.png",
"scale": 0.5,
"mipmap_count": 4
}
],
"color_hint":
{
"text": "I"
}
}
There isn't any risk, because another mod depending on RO will always run its data-updates.lua after RO's data-updates.lua. Factorio ensures this. It's largely why optional dependencies are a thing.
It's called data-updates.lua for a reason: That's where you update things, whereas data.lua is where you define entirely new things. When done correctly, it enables us to navigate situations such as this one, but also it allows mods to interoperate without explicit dependencies.