OK, I'm trying to clear out some backlog and came back to this. I think the right thing to do here is just comment out all of the entries in the elevate.xml config files.
The trappy bit is that a user whose never even heard of QEV changes the <uniqueKey> to something like "long" and suddenly can't load the core or create a collection. Because we've included an example elevations that are only relevant to the sample techproducts docs.
If someone intentionally changes the QEV component then I think the stack trace is sufficient since it makes sense in that context. And at least they're working with QEV so have incentive to look.
I'll check this in tomorrow sometime unless there are objections.