I would really appreciate somebody developing a good hiking profile. That should probably be based on the new versions lookup-table, where the hiking relations are available.
I had a look at your version. Some issues I noticed: It seems incomplete in the access rules (avoiding access no/private on nodes, but not on ways?). The elevation cost for a walking profile I would expect to be lower than the downhillcost=60 from the bikers profiles.Costfactor 20 on primary roads I think is too high.
And a noticed a technical problem: by starting the costfactor term with:
assign costfactor
add switch foot 1 1.1
and then continue to add at least another "1", your costfactor is at least 2. But for efficient calculation, the costfactor should be close to 1 for the type of way you are looking for, otherwise the processing times for large distances go up.
So to make a pure technical adjustment for that problem, you could divide all numbers by 2, including the downhillcost and you should still get the same results. (That relates my above remark on the downhillcost...)
regards, Arndt