I disagree with Gordon.
Generating bindings is a client development activity in my view. With the .i files exported in this way developing bindings is no longer restricted to those with access to the qpid tree, but the only requirement to develop a new client binding is the client include files.
This strong decoupling is a very good thing from my point of view.
Obviously you wouldn't export .i files that relate to individual bindings to the include files, but the .i that give the general typemaps that are useful for every binding and point at all the necessary include files seem like very good candidates for export to me.