I suspect you've misunderstood something here. Config views are intended as a way of describing the rules by which a design hierarchy is expanded, and are typically consumed by tools that need to expand the hierarchy (such as the netlisters used in ADE L/XL/GXL). So it's reasonable that ADE XL allows you to describe one or more tests where the design is specified as a config - and that will tell it how to expand the hierarchy (which views you want to simulate) for that test.
It makes no sense for a config view to reference an ADE XL view. The ADE XL view is nothing to do with the design hierarchy - so I can't see why you'd ever want to do this. What would you expect to do with the resulting config? If you consumed that resulting config in (say) ADE XL, what would you expect it to do when it encountered an ADE XL view in the config? Especially as the ADE XL view could be describing multiple tests, each with different designs.
So I think you're probably thinking about this back to front. You use the config to describe the hierarchy expansion, and then reference that config from the ADE XL view, not the other way around.