Charlie,
Thank you for the clarification on the support dates.
As to the onRequest() vs. onRequestStart(), you are correct that you must have a <cfinclude> in the onRequest() method to actually load the page requested like so:
<cfinclude template="#ARGUMENTS.TargetPage#" />
However, nothing prevents one from putting additional <cfinclude> tags either before or after the one that calls the TargetPage. I have an application that has run for more than 10 years that had two or three additional <cfinclude> tags in it to load some common "chrome" to the site. Should those have been in onRequestStart() instead?
Ok, but I was neither saying nor implying the contrary.