re initial disregard of Paved setting: as you say, the suggestions disregard a Paved setting and behave as if Any was specified. But when a suggested route is selected, clicking on Paved adjusts it, so its only one extra click, albeit somewhat odd that the initial "Paved" is ignored.

re weird results: It's not a function I use, as - regardless of the Any/Paved aspect - the results look a bit unsatisfactory when I generate them for an area I know. This seems a bigger issue to me. eg for Ponteland, on NW edge of Newcastle - so a gateway to lovely cycling territory on the little roads of Northumberland - many of the suggested routes seem drawn to the dedicated cycle paths of the more urban parts of the north east, which seems unhelpful. Ideally, perhaps something in the algorithm could be tweaked, to turn up a "prettiness" weighting? That would seem to better reflect what CTravel users are likely to be looking for in these circumstances. (However, I also appreciate there may well be underlying technical reasons constrain what is possible - and RF's time resources, too...)