Problem with Rawtherapee packaging

I've been using Rawtherapee (RT) Portable but have encountered a problem that needs attention.

Apparently the developers of RT have decided to abandon|stabilize the 32bit version. It appears as though this has caused Portable Apps developers to distribute both the 32bit and 64bit versions as part of the same package, where the decision about which version to launch being controlled by the architecture of the computer on which it is being launched. The problem is that there are compatibility considerations between the 2 versions which affect which one the user would like to use. Possibly my problem is that I simply don't understand how a user of portableapps can choose which to launch.

IS IT POSSIBLE FOR THE USER TO CHOOSE WHICH VERSION GETS LAUNCHED? IF SO HOW?
Even if this is possible the user needs to be made aware of the difference.

With that said the best approach would be to package them as separate apps. The reason is that someone, like myself, who is using the 32bit because the 64bit version doesn't work on their computer might, on some occasions, move to another computer that is 64bit to do some processing (i.e., this is the reason for liking to use portable apps). They would expect their work, on the 64bit version, to be compatible with work done on their usual computer and would often intend to transfer that work product back to the usual computer. This won't work in the case of the existing RT portable app. Furthermore, unless the user is very savvy they are very likely to be deceived. In that RT will appear to working fine but it won't tell them that the resulting work is NOT interchangeable with the work they've previously done with the 32bit version. In this scenario the user wants to continue using the 32bit version even when working on a 64bit computer which should work just fine. Another scenario would be transferring some work done on a 32bit computer for further processing to another computer that happens to be 64bit. RT would make it look like this is working and attempts to understand the processing profiles created by the older version of the software but the user cannot count on the 32bit work being accurately duplicated on the 64bit version. Another similar scenario would involve a user who normally works on a 64bit version who would not want to be similarly deceived when they find themselves on a 32bit computer. While they won't be able to work with the 64bit version on the 32bit computer this is what they should learn immediately if they should try and do so. In that before attempting to do any work. As mentioned above the work, done using the 32bit version, cannot be reliably moved back to a 64bit version even though the 64bit version may appear to work correctly when this happens.

Bottom line is that with RT the user needs to be in charge of what version is being used and it should not be something that is taken out of their control.

When it comes the possibility of finding a temporary workaround for this problem, it would be very helpful to know of the best way to disable one of the versions. IS THERE A RECOMMENDED WAY TO DO THAT?