I don't see why this could have anything related to the KORD scenery, which has a perfectly legal AFCAD that is correctly recognized by FSX, so the problem clearly is not the scenery but, most likely, if that Radar contact program reads a scenery AFCAD, that has a problem that is being confused by an otherwise fully working AFCAD.
Some things that might cause this (and if this is the case, the problem is surely not KORD scenery), is the fact that KORD AFCAD use the very well known "star technique" to allow crosswind runways.
Another potential issue is, since new runways has been added and old runways has been renamed, KORD AFCAD also comes with its own set of Approaches, which overrides the default FSX ones. If that Radard contact program relies on its own internal database of approach procedures or it reads from FSX, but only from the default set of AFCADs, it might still see the default approaches, but those are not working anymore in the scenery, because their associated runways are not there anymore. Again, if this is the case, it's not obviously a problem of the scenery, but a shortcoming of that radar contact program.
Sorry but, since I've never seen it in action, I can only guess what might possibly be a problem for any program that is likely to to interact with the approach procedures.
