Oh, believe you me. Currently, our "non-legacy" CF apps utilize a much proper URL rewriting. We use IIS' URL rewriting engine to check and modify the incoming request to a CF page, which then allows CF to take over processing the request. This allows us to use the RegEx for powerful matching, as well as file/directory checks before the request is rewritten. A MUCH better solution to this legacy app (which for time constraints, we cannot put into our new framework, but are looking for the quickest solution to get it over and running). This allows us to use "Pretty URLs" like domain.com/blog/2013/september/15/this-is-the-title-of-our-story (No .cfm in the URL).
Oh, and please don't take what I was saying as offense; I'm actually completely on your side. Cost-wise, it's sound, and comes down merely to a matter of time. Management is a bit..peculiar about that, to suffice it poorly. 
Sadly, I learned CF "as I went", and really wish I had a more proper and structured acclimation to it. What I do know, I love, and what I keep learning, I love even more. I just know there are tons of functions and methodologies out there to really optimize my applications; but the web team here isn't as enthusiastic about my method as I am, and instead, prefer to "look it up as we need it". 
Ugh.