Your italian is very good but, the forum language is english, so anyone can read what you are saying. You are welcome to write to us using PM or email in italian, if you like to do so.
To reply to your question:
First, as you should know, FS9 and FSX do not support operation on multiple runways. The way they are implemented in AFCAD is really a hack, that has side effects, and we would prefer not offering such AFCAD by default. You shouldn't complain about this scenery, because the issue is the same for any other scenery. Of course, simpler airports with less runways or even just one runway, will not show this problem, but the real issue is the underlying AI engine, that we can't obviously fix, without resorting to the aforementioned hacks.
However, you will find several discussions about AFCAD made by Harpsi, that use all kind of methods to use multiple runways, depending on wind, etc. If you follow the discussion ( is pinned on the O'Hare for FS9 ), you'll realize what the issues are and what solutions are available.
Unfortunately, Harpsi stuff is for FS9 only. Since Harpsi is just a user like you, sharing his own creations, and it's not part of FSDreamTeam, we can't force him offering the same for FSX. Who knows, in time, he'll switch to FSX as well.
Why don't you simply try editing the AFCAD yourself, like Harpsi does, for FSX ? As I've said, FSX do not support x-wind runways, that's why we don't think we are supposed to offer it as standard.
Another solution to the long takeoff cues is very simple: lower your AI density. FPS will benefit as well.