No, there’s no way to do that while still keeping the functionality your customers are ‘implicitly’ asking for. The only ‘wrapping’ in MSI you can do is to extract it on installation and start your InnoSetup installer from the temporary location where you extracted to. MSI is a fundamentally different way of working: InnoSetup (& NSIS & most other installers) take a code-centric approach: you ‘program’ the ‘steps’ to install your data. MSI is a database and takes a ‘data-centric’ approach: you indicate what files should be installed and the MSI ‘runtime’ does the rest. This gives you versioning and exact control of what goes where.
In short, to give your customers what they want (i.e., the ease of deployment that MSI brings with AD), you’ll need ‘proper’ MSI’s. Good luck with that, it’s a major pain IMHO. But it does give good results once you master MSI & WiX.