I'm talking more about the distinction between VB/DOS and VB/Windows. They both did the whole WIMP thing, with a visual editor to construct the forms for one's programs, but VB/DOS used a TUI rendering that drew everything with VGA character graphics and used the firmware low-level keyboard access for input; whereas of course VB/Windows used the Windows GUI.
A VB/DOS-alike that ran on EFI and did the whole form-based programming thing, would use the EFI text input and output protocols, which know Unicode, waiting for events, and standardized scan codes and modifiers.
There is no major call for it, as you say, when bootstrapping an entire operating system is so easy. But it would be interesting to see someone tackle it from the point of view of what VB/DOS would look like today if it ran directly on the firmware, spoke Unicode, and ran in protected mode