So my question to you is why are you transporting into another Dev system after the proj QA release? The SAP E2E200 session points you to having a project landscape go to pre-prod only to validate that the changes don't cause chaos within production.
If you have constant changes occurring on your BAU track, then you should be retrofitting into your project track to avoid overtaker effects on the project imports.
Then after your project transport into Prod, you take the project dev/QA systems and refresh them back to BAU to keep object versions in line with production.
One bad thing (imo) about how your transport process is currently, is that your objects in Dev BAU are not in sync with Prod for a short time. And then you are prone to an overtaker transport if an emergency one takes place while testing of the project transport is still on QA BAU. While pre-prod would catch this for, you still have the potential for a 'perfect storm' event even on pre-prod. Ideally you want to get approved changes to production as soon as possible to keep everything in sync.
