Let me say, start the New Year with a post is a good start. What do you say?
However, from my experience if fails with a Timeout during the XPO Import (you can achieve this through the Build Txt log), the reasons can be two:
1- Someone delete an AOT object without commit the operation on TFS. Afterward someone else create a new AOT object and add it to TFS. This one could have the same GUID of the deleted object.
2- Someone rename an AOT object but on TFS (through TFS Solution Explorer), the object have the new name but inside the XPO is present the old name (In my opinion this is a Microsoft bug)!!!
In order to understand which object create the issue you have to:
1- Restore the AX Baseline Database (the DBs without any AX Customizations) on your TFS Build AX Environment
2- Run the XPO Import process manually and verify the error
3- Fix the error on Dynamics AX or TFS as mentioned above
4- Rerun the TFS Build Process