I was waiting for you to give an example of an "event driven language" to see whether I understand what you're asking. But I decided that you probably have some misconceptions. This first sentence of your question makes sense, "I'm meant to evaluate the suitability of event driven programming in non graphical applications." But then everything you wrote after "All I know..." is confusing and probably wrong.
Event driven programming is a design style. I don't know what you mean by event driven language and I'm skeptical whether that's a thing.
Event driven programming is very suitable for embedded systems because many embedded systems are event driven by nature. An event can be a button push, sensor detection, received network packet, timer expiration, etc. Think of an elevator, printer, or wireless router.
Miro Samek explains this well in the first couple pages of the Introduction chapter of Practical UML Statecharts in C/C++, which is subtitled "Event-Driven Programming for Embedded Systems". (You can read the Introduction from the Amazon listing if you click on the "Look Inside" link.)
Event driven programming is commonly used for GUI applications because it's very easy to do so with tools such as Microsoft Visual Studio. Every beginning desktop application developer starts with event driven programming and has access to a multitude of examples.
Conversely, a beginning embedded systems developer typically writes a main super-loop to blink an LED. Embedded development tools don't provide the event driven framework like Visual Studio does. And examples of event driven programs are uncommon. That might explain why event driven programming is less common in embedded systems. But it would be wrong to say that event driven programming is not suitable for embedded systems.
Edit: You've changed the question. I don't understand why you originally wrote "event driven" when you were asking about VB.NET.
VB.NET is not suitable for typical embedded systems but I don't believe any of the reasons are related to the concept of "event driven". Here are a few ideas you can research further. Programs written in .NET languages run on computers where the .NET framework (CLR and FCL) has been installed. The .NET framework does not exist for smallish microcontrollers used for many embedded systems. Embedded systems often have limited resources in terms of memory and CPU power. The .NET framework and .NET programs are too resource hungry for these resource limited systems. Embedded systems often have real-time requirements. .NET features such as garbage collection make it non-deterministic or difficult to ensure that timeliness deadlines can always be met.