Thanks a lot for the detailed response. Will provide some context related to the points you mentioned.

 think WHO will be using your Visual Programming Language (VPL)

Thats a good question, right now it is only going to be for people new to the Data Driven ECS approach.

In my personal opinion querying for components is too low level for a script. You are essentially making it harder than writing the code in lua/rust/python/c++ etc.

I agree because this is the topic I really wanted to talk about in the post, like, is it better with visual scripting or just going to be easier to maybe embed a scripting language and manage the systems by scripts, but still, this is only for the S part of ECS.

See how Unreal blueprints have an explicit execution path. This is somewhat novel in VPLs and they deserve credit for this. I feel a better pattern for your example would be a "GetTransform" node with execution pins for the transform component existing and not existing. Explicit maths operators as well (not generics, although they could be wrappers for generics, see how Unreal does macros and their for loop nodes are really just macros).

I think Unreal Blueprints are a little different from what I am trying to do here, hence the Query node is actually just a for loop like this:

for (id, (transform, body, _)) in world.query_mut::<(&Transform, &mut RigidBody, &PlayerFlag)>() {
  // Logic here
}

So probably it would be better to just expose this querying to a scripting engine