You are sharing quite a lot of files, right?
aMule works event based. Most actions (except upload) are processed in a single foreground thread. If a timer fires, a network packet arrives or you click on something it generates an event. These are processed one after another.
For this to work aMule should make sure all these events can be processed quickly. Otherwise timing critical things have to wait too long. You click somewhere, nothing happens. Someone sends a packet, gets no reply, drops the connection. Statistics get wrong results because timer events don't get processed.
Example for something that takes too long is when a file gets completed and has to be hashed. Such things do get processed on a background thread to avoid such problems. But this takes some complicated setting up, messaging, signaling when it's done and so on.
Bottom line of what I'm trying to explain: sending the shared file list with many files may very well be an operation that should better be processed in background. (The actual sending IS done in background, but the compilation of the list isn't.) It isn't because nobody bothered, because it only rarely happens, and most people have totally disabled it anyway. And if the only bad thing happening is a temporary glitch in the Kad statistics, I'm seeing no reason to change the behavior.
