I have not been able to use the scenery since I purchased it.
"Not being able to use is", it's really over the top. The scenery is obviously usable as it is now, and everyone is using without any issues.
I work at LAX and most departures and landings are to the west (toward the ocean). Not as it was in the file we all purchased. Departures and arrivals to the east are only after 11:00pm, due to noise abatement, and when the weather changes drastically, such as thunderstorms. Take offs on the north side are relegated to Runway 24L and on the south side to Runway 25R.
I'm sorry, but this can't be entirely fixed because how FS9/FSX works. It's not possible to just close a runway for takeoff/landing, the "close" flag will only affect the runway scoring with its weight, but there are other factors too, like distance from the gate (for takeoff) and of course wind.
The only way to "fix" would be altering the runways sizes, forcing Flight sim to prefer some runways, but that would mean both ends will go down in usage.
This is not really the place to explain in detail all the issues of runway selection, if you want to know more you can search or ask on fsdeveloper.com forum, were there are many AFCAD expert that will confirm this is not as simple as it sounds and we must accept Flight sim limitations.
So, the AFCAD improvements will act mostly on jetways (which is why I've said it would break AES it it was already released, but this is FSX only), parking sizes/types and perhaps airlines assignments, but not really runway usage, surely not in the way you would like it to be, because it's not really possible in FS9/FSX, unless using multiple AFCADs and switch between them.