I tend to agree with the way you put it, that w/ bitlocker or w/o bitlocker, they are both under the hood of device encryption, while one is for home edition, and the other is for pro and above editions.
Here is the thing though - In the "learn" sub domain of microsoft.com, these articles are all for commercial users (non-Home edition). Home users' articles are in the "support" sub domain. Hence, the article you referenced is focusing on bitlocker device encryption. So in that context, "device encryption" is like you said, the hood, and the article is all about the bitlocker branch because this is for commercial users. This is why the disabling instruction is also specific to bitlocker, because there's no reason for them at the "learn" sub domain to talk about home edition device encryption.
This is why it says "device encryption" (under the context that it refers to bitlocker specifically) does NOT protect when you use local account, because there's no way to generate the bitlocker key.
But otherwise, outside of the "learn" sub domain, outside of the commercial users context, it is not really correct to say device encryption IS bitlocker, because home users don't have that.
This really leads me to the frustration of Microsoft's naming strategy. It is super confusing, just think about all of the different Outlooks, Teams, Copilot out there. They can mean so many different things in the MSA and AAD world.
It's unlikely that a Microsoft employee, especially one from the encryption team, will join this discussion. After all, this is a community forum, and if they do happen to see this thread, any participation would be in a personal capacity. Typically, other Microsoft employees involved here are forum moderators who help maintain the forum's operations.
It sounds like you are building computers and selling them, any chance you are a partner already, as you can get more support directl from Microsoft. If not, you can check it out in case you are interested: https://partner.microsoft.com/en-US