If the problem happens only after a while, it's unlikely a conflict between the scenery and UT2, and the pause is caused by UT2 alone, since basically all the scenery objects are created immediately as soon as you enter the scenery area, which in case of KDFW is fairly large at 16 nm, once all objects are created, there's almost zero Simconnect activity on our part, even the active Docking systems and the special custom runway lights don't use Simconnect, except for querying the AI positions but, it's the same if the AI were default and, since you said that by removing UT2 the problem goes away, it means the scenery itself is not causing any problems with AI.
What happens if you simply lower the AI density in UT2 ?