Yes, i'm not a guru. I have some background in winpe ( i use it from the first OPK ). For using in my company, in the past, I put dotnet2 and Powershell in winpe3; i make a "specific" winpe for the configuration of RAID5 card...Now i'm retired.
My English is not good. Sorry. If you don't understand what i write, please, forget me.
If my company gave me your goal, i asked :
- first: why winpe64 for launching only one 32bits VB6 application ?
- second : which limit/size ?
- third : i'll start from a winpe that ADK products ( with only the needed packages ) . And i'll use procmon to "trace" the application for needed files/registry
- forth : why the need of "explorer" : desktop of only the "openfile" window (notepad or a vb6 to launch it)? Slore's WinXShell can be good.
The syswow64 is populated in the winpe from ADK ( i verify in a boot.wim but i added many packages ). The VB6 application needs only a few of them...or some new files.
After, i'll search all big directories, drivers, drivesStore, config... modify system hive for unneeded drivers; search unneeded files.... but it's long.
note : imageres.dll size = 15Mo in winpe from ADK and 23Mo from winpe10SE ( it depends on scripts you use )
Perhaps i don't understand your question… so, don't be angry.