The configurator is really a C# runtime environment that is spun up by the client, and then the configurator code is downloaded from the server and runs. It is cached on the client and checked for proper version so it will run faster, but even that takes a few cycles.
It’s pretty much a pain when you have a small configurator. Ours are quite large/complicated, but load almost as fast as yours, so I would say there is sort of a “minimum time to load” that we all experience.
If you are just changing a description value, could you do a BPM that presents a BPM form and uses the widgets to overwrite the description? I’m not sure about your exact process of course, so I’m not sure it would fit in but something simple and easy to consider.