In my case the results are the same - Windows boots without error. I have never needed the other files contained in the boot directory in my setup - so I decided not to add them. For those that do, then use the following entries in the [PrepopulateList] section of your .ini file -
Very good , but what I asked was (slightly) different. (please bear with me )
Let's put aside for a moment the "wimboot".
If you "install" a Windows Vista :ph34r" or 7 (and I believe this is the same for 8/8.1) the "quick way" is to (simply and rudimentally) apply "normally" the install.wim and then run bootsect.exe (if needed) and bcdboot, like in:
imagex f:\sources\install.wim 5 c:
bcdboot c:\windows /s c:
bootsect /nt60 c:
or, in the case of 8 (or with previous versions as long as you use the 8 DISM), one can also apply the wim with DISM, with something *like*:
DISM /Apply-Image /ImageFile:D:\sources\install.wim /index:5 /ApplyDir:C:\
The install.wim is seemingly NOT containing a BOOTMGR and a \boot\ directory in it's root, and after you have applied the image there is no trace of these files on the "target" disk partition.
When you actually run the bcdboot command, the "target" disk partition gets added the BOOTMGR and the \boot\ directory, this latter containing, besides the BCD, a number of files.
From your report I gathered that only the BOOTMGR and the \boot\BCD files are needed for booting, did I get this right?
I.e., in theory (generically) one could replace the Bcdboot command with plainly copying a BOOTMGR to root and use a BCDEDIT script (or some of the other tools) to create a new BCD, or am I missing something?