Hello and Thanks, @abcoathup !
Perhaps we should migrate but it doesn’t seems like an option at the moment. 
Our use case is simple, we have this (proxyed) contract which is part of a set of components which connects among them. It doesn’t really matter what the components do, but what actually matters is that it have to interact with an external (out of our scope) contract (a basecoin wrapper) and call its withdraw, which finally calls a transfer(…) to us. We reached this problem: Msg.sender.transfer runs out of gas on a payable upgradeable proxy contract and thought it would be useful for us to prevent the transfer callback: fallback to be proxied.
At the moment, if we continue with the option to use a custom (fallback blocking) proxy, seems to be to deploy it by hand and then configure it point to the implementation (also deployed by hand).
But I would prefer to use the standard createProxy(…) functions…
Thank you!