Same here in Thailand. We have well-known routes that require navigating long, pathless stretches of dry riverbeds and mountain ridges to reach the next visible path. Apart from traces of boots, wheels, or cattle, there’s no clear indication of a path, and the best route can change by a few meters yearly after the monsoon. However, the terrain’s geometry usually suggests the best recommended path. Without these routes marked, people might still try to connect and end up on the wrong adjacent ridge or riverbed.
I get that they might not fit the typical highway=path tag for regular users, but leaving them untagged could mislead others searching for the right connection. Supporting trail_visibility=no in third-party renderers/routers still seems like the best solution to me.