InstrumentationHelper#populateExisting is inconsistent in some environments

From xxDark

> `populateExisting` will not work as expected in environments like launchwrapper and all this stuff, better approach would be to ignore VM generated classes for lambdas, proxies, etc and call retransformClasses on all classes (calling retransformClasses on VM-generated classes will cause it to crash because some constants are injected using cpPatches (e.g by InvokerBytecodeGenerator))

Start at InstrumentationHelper#populateExisting and inspect how it selects classes for retransformation. Compare its behavior in launchwrapper-like environments with the constraints around VM-generated lambda and proxy classes described in the issue. Done means the inconsistent behavior is resolved without retransformation crashes, but the issue does not name tests or a specific validation path.

Written by the indexing model from the issue text.