That’s exactly what I did.
If you look at the guidelines, you’ll see that trails info should be in the relation.

A relation should aggregate several small sections of ways.
A relation is a means to have the same info applied to several features (nodes and ways)

It is not just a “best practice” - This is how it should be done in order for it to be mapped in a standard way,
so all renderers (e.g. Mapnik, Osmarender, CycleMap, Lonvia, hikebike.de, etc) are aligned.

You added a path (i.e. Single) which intersected a track (i.e. Double)
A common practice is to cut such paths.
And also - The path hit the track at one point, then it overlapped the track, and continued from another point.
So it’s really two different paths, with one track.

Another good common practice is to cut tracks whenever they cut other tracks, and to cut paths when they hit other tracks or paths.
off road ways should be as short as possible, between two intersections.

What do you mean by “OSM viewer”?
Mapnik? You can’t control it. Tracks and paths appear at zoom level 13.

Lonvia’s displays relations. See above. :wink:
Now that the data is in a relation, Lonvia’s would pick them up and show them by tomorrow.

talkat.