Do I need to "align" wim or bcd to wds to make the x86 image "accessible" to uefi(64)?

Question

PXE

speech about images of loading , instead of installations (2nd stage)

wds works normally.
and uefi and legacy clients are automatically (by broadcast) detected and loaded

problem in different boot menus. in legacy all 4 images are available (3 x64 and 1 x86) and in uefi (it is assumed that 99.9% of clients still support x64) only 3 options for x64
and x86 is also needed (I couldn’t mount a 32bit prog on x64 PE)

How to fix it?
It's obvious that x64 is backwards compatible with x32. which proves the legacy mode.

wds itself is dumb as a cork - everything is "automatic"

Answer 1

for some kind of demon, they really made a fierce incompatibility of x32 and x64 for uefi ,
the menu items themselves found how and where (bcd are generated on the fly and are in the tmp folder, but you can rename it)
there were similar questions all over Google but 0 answers. so consider the "pioneer"
another thing, which is meaningless in the end. "Starting" is loaded in x64 - does not digest x32 efi program
even changing winload.efi - we run into ntoskernel.efi, and changing it is useless.