To test with chrome you don't have to do much other than make sure your object works with IE. And UFT patch is up to date with chrome, since it's hard to go back in Chrome versions. In my experience chrome browser had better performance than IE.
I haven't used QTP/UFT browser compatibility features in the past. I'd probably would still refuse to use them today if I was still using QTP to avoid coupling the tests to the tool.
But I've supported multibrowser using QTP without their browser compatibility features. To do this is pretty simple, use shallow find operations (descriptive programming) to locate objects relative from the 'Page' object. All the stuff above the 'Page' level can vary between browsers. Those parent objects are things like process, tabs, windows, containers.., all of which are not dictated by the DOM, while everything under the Page object is dictated by the DOM.
On a separate mapping, map the Page Object on all the different browsers you support, and in your tests, use a Factory pattern to instantiate the browser page object. From there all your relative descriptive programming mappings will work.
This will allow you to support multiple browsers, even ones that QTP doesn't support. This technique works with many native testing tools as well.