What I am saying is this we write our application to integrate with vbulletin. Our application performs flawlessly with vbulletin.
Your issue as I have said a few times here is with the use of code hacks or mods for vbulletin. We can not find or duplicate any issues with our code and vbulletin.
It is not our responsibility to fix issues that arise from the use of code outside that of vbulletin and ours.
I see your flow chart. However there is no issue with registrations or anything with vbulletin and vbgallery when testing our applications together. I have already done this.
If you get errors only after adding hacks then the real fault here is the hack not our code. Do you understand where we are coming from here. if there was a real problem with our code we should be able to duplicate issues with our code interacting with a clean vbulletin/vbgallery install. Simply done we can not.