I came across this issue recently and it made me think of the orphan compatible MSI package feature from VS that I pulled a while ago because it was running packages that weren't in the manifest. Can we loosen that restriction, or is this issue also not possible to do securely?