again, to me, you're just not making sense.  you're coming up with a solution that needs content editing, when in point of fact that's just not necessary or beneficial to content owners or creators. yes, every render engine has something special.  which is why the content should be renderer agnostic.  just leave the content alone, which you'd have to account for anyway, and let people select the special treatment themselves.

it seems pretty trivial to have a tab for different types of treatments and a list of materials to check with a default of nothing checked or guessing by some basic material property, including name.   it would make more sense to detect things VSS string evaluation style than some artificial prefix.  like bulb, glow, light, flame, etc. for lights, skin for skin, etc.  and personally, i've never used ambient for anything that doesn't glow in all my years of using Poser.

it seems simple to implement, necessary for legacy content, and doesn't make the content renderer specific.