I think the detection should certainly trigger before the wrapper does anything;
This is almost certainly not realistic/practical.
The wrapper is going to do its own thing, and then unpack and launch your original pristine installer after it has offered up its bundled adware, etc.
If you wanted to physically stop the wrappers from running, the only solution is to have some other software already running (like an antivirus) that detected it and stopped it. And if you are the kind of person who would run such a tool constantly in the background, you are also the kind of person who won't get bit by these wrapped installers in the first place.
However, I believe that the solution with the dll preventing your program from installing from a wrapper and telling the user why will accomplish the same goals.
The most likely result of having this dll prevent the wrapper from completing its installation, is that it will never be wrapped in the first place.
First, it's quite likely that the automated wrapper creation tool will abandon trying to wrap your program, meaning you will stop this problem before it ever gets to the user. Second, if it they do try to distribute your wrapped program, it won't be long before they get enough complaints from users that downloaded it that they will remove the wrapper and put back your original.
