Pieter - thanks for the explanation about the placing of materials and the downloading for Enscape. I don't program, so I figured there would be a better way for Enscape to track which materials were placed in a model and key other users machines to download as needed.
The "additional render appearance paths" method is what I have used, but I'm thinking that only works for Revit material browser textures? That is where the Lumion export plugin helps gather those into a single folder for sharing with others. I haven't really dug into the Enscape duplication of the material library yet and how those textures work/interface with Revit. I guess I'm getting old enough to be a bit more stubborn in my ways 
Beyond the idea of making the same workflow across programs, I haven't figured out what the Enscape library advantages over the native Revit one are. I see that their library of materials is a little less dated than the standard Revit ones, but the functionality of the Revit material editor seems to have the same features so far (albeit with a few "quirky" workarounds and limitations for things like: displacement mapping, video textures, tinting, and procedural bump maps).