Just to clarify what 91.175(f) is referring to with regard to ODPs and climb gradients…if an ODP is published, that’s basically the only routing that the FAA has evaluated as clearing obstacles from that runway. No diverse departures are evaluated.
(f)(3) says that Part 1## operators are required to fly a departure path that has been evaluated and approved, therefore they must fly the ODP if one exists.
(f)(4) adds the option for the operator to create or purchase an alternate procedure that meets obstacle requirements (separate from TERPS, actually...that’s the Advisory Circular mentioned), but that includes knowledge of where the individual obstacles are located.
Since Part 91 operators are not required to fly the ODP, implication is that there are other acceptable ways to clear obstacles, and you can use local knowledge or whatever means to determine an alternate procedure without the requirement for specific FAA approval. As long as you don’t crash or consistently set off altitude alarms with ATC, they probably won’t concern themselves with exactly how you depart.
Keep in mind, also, that there may be “close in” obstacles within 1 mile of the departure end of the runway, up to 200 feet tall, that are not included in ANY climb gradient evaluation that the FAA has done, whether ODP or standard 200 ft/mile. To look at your KTVL example, runway 36 shows these:
View attachment 97237
since most takeoffs don’t use every foot of runway, the FAA allows you to use the runway you don’t use to reduce the climb gradient required, and so these close in obstacles are often not an issue.