I see what you're referring to on the redundant relations and agree. I didn't make any changes to the structure of the relation so I can't speak for which one is the correct one, but I trust your judgement.

As for the naming, my opinion is that "cycling" and "hiking" are descriptors that are not officially part of the name, and therefore do not belong in the name tag. route=hiking and route=cycling are already in present and function to differentiate. I would go so far as to say it's redundant to have separate hiking and cycling relations. Why not just have a single relation structure, all tagged with route=hiking;cyling? It would still render on both the hiking and cycling waymarkedtrails, and prevent users from accidentally adding members to the wrong relation should the trail be rerouted.

Of course, this is a much larger change that I would suggest discussing in the NY State slack channel at a minimum.