MicrosoftI personally think that this move to LAMBDAs is a way to move away from VBA. I also work in cybersecurity, and macros are an enemies, not friends... They are more and more blocked in organizations.
If you have to register a LAMBDA like any other add-in, you're not on the correct path. Why Microsoft would have developed LAMBDAs function if you have to do like any VBA Module ?
My view is that because cybersecurity concerns will kill VBA one of these days. All the set of the features are there for that (LET, LAMBDA, PowerQuery, JS API, ...).
That's true that the Name Manager is very limited for development purpose. Maybe a "Function Manager" will born as an extend of Name Manager to provide the different missing features we've been talking about here.
That would be maybe the best solution... a new window to configure, document the LAMBDA parameters, optional parameters and default values. Even if after, it's handled by Excel as it is right now, as a Name. The new window would format all the data correctly.
