The ferry route has an access point for vehicles and a separate one for people on foot. The issue before was that the small way 469672195 was tagged with duration=1:00 and then the actual ferry route also had duration=1:00 so that the total ferry trip would take 2 hours for someone on foot.
I solved this now by giving the short ferry way a duration=0:01 tag. However I am not sure this is the best solution ? Another idea would be to create another ferry route right next to the original one, but that would just be two ferry routes which are the same anyway.
I would say, that https://www.openstreetmap.org/way/469672195 is not a ferry but a (partly virtual) footway.
The second motor vehicle ramp (https://www.openstreetmap.org/way/37434461) is not connected either.
Sorry, I am much more familiar with train and bus route tagging regarding public transportation, so I have no clue how you get a connection between the three ramps as one stop position.
As the ferry route is already mapped as an incomplete route relation (https://www.openstreetmap.org/relation/311463), I would fix it and move all the information, or at least the timetable tags, onto the relation which can have several connected route=ferry ways as members. I think the toll=yes should be added again which was removed in the last change or is there no fee to pay?
Add to a type=route to collect them first. For the perspective above, There is a virtual=yes idea that I liked for highway=.
Another not uncommon situation is multiple berths used by frequent services requiring simultaneous dwell on a finger pier
Personally don’t fully understand why route=ferry has to be directly connected to be routable. Cf how is Eurotunnel Shuttle train terminals handled now? Unlike public_transport=stop_position, seamark:type=berth can be drawn as an area.
Railways have =platform_edge for continuously accessible sides on an island =platform.