I don’t know if you could find a way around this. I tried to do the same and run into the same old "Oh, but you should use xyz instead of" answers that don't help. In the end, I simply created a deployment manifest using BIDS and then copied it to the solution directory. It never changes (at least for our packages it’s not), and since the build command does not actually do more than copy the dtsx and config file to a folder and write xml for the deployment manifest, it makes sense to just ask my the build process is to copy these files, including my previously created manifest.
It also allowed me to edit confidential information (i.e. the name of my domain account and the domain name itself) from the manifest file. The only thing is if you significantly change your package (for example, renaming it), you will need to create a new manifest using BIDS, but this is the best I could come up with, and I could not justify more time spent searching differently.