I think the whole 35 in dry and 15 in wet is ridiculous. Maybe I'm naive but wet or dry has absolutely nothing to do with the obstacles that you're trying to clear. The USAF and USN start with a screen height of 0 feet. If they have to raise it to clear an obstacle they annotate with a "Trouble T" and further explain in the non-standard takeoff minimums. The FAA and US Army commonly raise the screen height without annotating, so if I see that the approach was designed by anyone other than USAF/USN I always put 35 feet in the screen height told calculation (unless it clearly states otherwise in the "Trouble T").

Think about it this way. When you start out from a point in space and climb at 200'/NM you may not clear an obstacle. If you raise the point at which that vector starts ( to 35' or whatever) you may clear the obstacle. This is why TERPSters raise the screen height (whether they decide to tell you or not). When you subtract the 48'/nm "buffer" you get divergent vectors. How does this have anything to do with the runway being wet or dry. I'll agree that runway condition definitely affects AccelStop or AccelGo or Balanced Field or Critical Field Length (all basically the same idea).

Unless you're really sure about what you're saying please don't write confusing info that may get someone killed.