I think inline node options will be here for a long time or will be removed with some general handling of older files, in another hand todat this is more complicated dealing with the node and…
For me its just more complicated if params is crawls more deeper and deeper in a stack and its better to just pass all such arguments from the top level where simple switch can be.
We need to transformation * ~transformation so here is not accurate unit matrix in result, does not seems like good thing to be used as interface of operation just to skip coping.
Shouldn't this be at geometry nodes modifier level? I do not know is there is any such case but it seems like invariant of unique names also can be used in other modifiers that would wrong with this change\
const GeoNodeExecParams ¶ms -> const Field<bool> &selection_field
/* #join_geometries can skip such case but transformation can not be skiped later for free. */
Simulation zone takes the input value only once, after that value is keeped as-is in the zone loop, read geometry just by zone-dependent nodes.
As i can see here is the same issue as was with UV custom data, this simply not an attribute.
Do not recreate node every time, just move old one to a new place (#121951), use viewer by clicking on a socket, eye icon in the header, ...
In geometry nodes we have specific behavior of the viewer node which is probably should be used and in compositor.