Question about core_template_route hook

I’m trying to write an extension using the core_template_route hook. Whenever it changes the template that is being loaded, it appears to load the page properly, however several things don’t behave properly:

1) Dynamic channel entries always load the most recent entry instead of using the url title in the third segment, even though the page can read and output {segment_3} correctly. 2) Any search I run results in an error 3) Pagination always stays on the first page, ignores what’s in the uri

I’m sure there are more. It doesn’t seem to be able to handle anything past the first two segments. Is this a common issue with this hook method? Seems very limiting if this is how it is supposed to operate. Any work-arounds outside of straight-up redirecting the user?

Thanks!