I don't know of any vendor doing much with 64-bit capture-type repackaging (as opposed to repackaging by wrangling the existing vendor-supplied MSIs various ways, and leaving aside the application virtualizers for a moment). EdT summarised the overall situation pretty well in this thread elsewhere on Connect.
While the learning curve is more like a cliff, really the most practical approach for 64-bit applications right now is wrangling MSIs various ways; Wise Package Studio is still one of the best tools around for that and can make it a LOT easier, although opinions vary as to how long it will remain that way. Given that you have a particular set of applications in mind, it's probably worth spending time on the AppDeploy.com forums since that's the best collection of reasonably independent advice on the subject in general.
Exactly how worthwhile 64-bit application capture tools are is an interesting question; I do think they do have a really important practical place. But they would be a difficult sell for any vendor that doesn't have an established management framework, especially with the big marketing and investment dollars going into app virtualization products like SVS and App-V which can and do promise the earth (and rainbows! and unicorns!).
As a historical note, for what it's worth I actually had mapped out a plan to replace AutoInstall (it had to be a ground-up replacement as there were too many fundamental design mistakes in AI as it was) to get 64-bit capability amongst many other things, and we were executing on it pretty well with it probably becoming visible in the next release after GSS 3.0 - this wasn't yet a PM-level feature (which meant no GUI tools until it became one), but rather something I'd arranged as an organic evolution so that we'd have application packages we'd be able to deploy in the preOSes (starting with the the management client itself, since we'd really needed THAT ability for a long time) which we'd open up and expose the scripts for once we'd dog-fooded all the new code, particularly the script interpreter I'd written for the management system - tasks as actual scripts being something I had wanted to do right from day one in 1998 when I started writing it - to a level we were confident in.
It's a pity the rug got pulled out from us on all that, but we *did* try.