The core team discussed staticallyCall and other variants that incorporated the word "static". The problem is that this can exist as protocol requirements and on classes, which are dynamically dispatched (through existentials and subclasses). We'd prefer to avoid the opportunity for confusion if possible.
Joe has some ideas (I don't know if they are baked or not) and would like to see the existing dynamic callable feature get revised (beyond removing the attribute and restrictions) to do something like kwargs in Python. This could lead to the existing entrypoint getting renamed, so I wouldn't over index on the dynamicallyCall entrypoint naming.
-Chris