Improve lwe startup time

Is your feature request related to a problem? Please describe.
Currently at my system it takes about 5s to start.
It's not an issue when start it once, and then use it for long time.
But additional 5s is too long if I want just run some non-interactive one-time request in command line.

Describe the solution you'd like
lwe is pretty complex, as my venv takes ~780MB.
And I'm sure that only small subset of all features are used for simple cases.
May be it's possible not to load all that huge megabytes at once, but only when really needed.

Describe alternatives you've considered
I am understand that this type of request may require too much changes, so...
I just want you to know that for some use cases startup time may be critical.

Start by profiling the lwe command during startup and identifying which parts account for the reported roughly 5-second delay and 780MB environment. The issue does not name files or tests, so map the startup path before proposing a scope; done should mean substantially faster one-time CLI requests without breaking existing features.