Well this article very much sums up what I have observed so far as in above post. In a nutshell, leave it to the websites to recommend the installation of the plug-in for the behaviour of the visiting site.
""Running Chrome Frame within IE makes many of the browser application's features non-functional, or less effective", Shaver said. "These include private browsing mode or their other security controls, features like accelerators or add-ons that operate on the content area, or even accessibility support."
He added that this could tend to confuse users and compromise their web browser security, saying, "As a side-effect, the user's understanding of the web's security model and the behaviour of their browser is seriously hindered by delegating the choice of software to the developers of individual sites they visit."
Because Frame-friendly sites come attached with an associated tag, Shaver explained that it would be better if website visitors were encouraged to install the plug-in as or when they needed it.
"It would be better for the web if developers who want to use the Chrome Frame snippet simply told users that their site worked better in Chrome, and instructed them on how to install it," he concluded."