I was planing to send a mail for the second unit test but it takes me too much time to merge the patch due to the network issue.
Here is my explanation for it, because Camel is using the RouteService to delegate the life cycle invocation, it is also in charge of do some clean up work with the CamelContext. If you just stop the route directly without through the CamelContext API, you will face a issue that the RouteService can not has the same status of the Route.
So my suggestion is you should use the CamelContext API instead of stop the route directly.
We should consider not expose the Route itself to client to use in Camel 3.0.