It's been more than a few years, and even now with Windows 10 the BCDEDIT program remains as mysterious as before. Slightly more than a year ago, I had to learn about BCDEDIT the hard way and I didn't have the faintest idea how BCDEDIT or BCDBOOT was supposed to work. To answer your question, if BCDBOOT can be used to create the template to make a bootable Windows entry in the BCD, then BCDEDIT can probably do the same with a lot more commands and typing, as follows:-
C:\>bcdedit /create /application OSLOADER
The entry {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} was successfully created.
If you check inside your BCD to find that particular {ID} which was created, then you will see the following:-
C:\>bcdedit /enum {43083ab0-6bcd-11e8-a9c7-9cb70d586adc}
Windows Boot Loader
identifier {43083ab0-6bcd-11e8-a9c7-9cb70d586adc}
You would be right to think that there appears to be a lot of information missing for a proper Windows Boot Loader entry in the BCD. The full entry should look something like the one that was created when you first installed Windows, as follows:-
C:\>bcdedit /enum {current}
Windows Boot Loader
identifier {current}
device boot
path \WINDOWS\system32\winload.exe
description Windows 10 Pro 64-bit
locale en-US
inherit {bootloadersettings}
recoverysequence {d3150567-fac9-11e7-a6a0-d6a823273fc8}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice boot
systemroot \WINDOWS
resumeobject {fbe9c9e8-fa42-11e7-a9a1-9cb70d586adc}
nx OptIn
bootmenupolicy Legacy
So in this case, you are now faced with a lot of typing required, as I would think that at the very minimum, your Windows Boot Loader entry must have "identifier", "device", "path", "description" "osdevice" and "systemroot". Therefore, you will now have to type something like the following:-
C:\>bcdedit /set {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} device <whichever partition this particular Windows installation is located>
C:\>bcdedit /set {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} path <wherever the WINLOAD.EXE file for this particular Windows installation is located in>
C:\>bcdedit /set {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} description "<give a name here, if you use spaces then the entire phrase must be enclosed in quotes>"
C:\>bcdedit /set {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} osdevice <whichever partition this particular Windows installation is located>
C:\>bcdedit /set {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} systemroot <whichever folder the particular Windows installation is located in>
Lastly, you will need to modify the {bootmgr} entry to allow a choice of operating systems, by typing the following commands:-
C:\>bcdedit /set {bootmgr} timeout 5
C:\>bcdedit /set {bootmgr} displaybootmenu Yes
C:\>bcdedit /displayorder {43083ab0-6bcd-11e8-a9c7-9cb70d586adc} /addlast
More information here:-
Adding Boot Entries | Microsoft Docs
They are slightly different tools, and they appear to be independent. Putting it short
bcdboot
tries to repair what already exists,bcdedit
enables you to directly alter the bootloader. – Doktoro Reichard – 2013-12-27T17:00:44.447