Once you send the user to a URL via inAppBrowser, the content is out of your control and your plugins are not available to the user.
What you may want to do is use an iFrame but this will only work if the destination url can be white listed. If you can't white list the destination URL (i.e. you don't know what the destination url will be) you're screwed. What you can do is use a static destination on your server and have your server load the content and feed that content to your app. This way, you're white listing your server and your server is feeding you the content it found. Mind you, I wouldn't do it as you've blown all your security and Apple probably wouldn't approve it (Google doesn't seem to share the same concerns that Apple has) but you could do it.