Yikes. I'm not sure we want to just catalog the configuration APIs without context. Most users shouldn't call these methods. Doing so is the easiest way to make the behavior worse. Instead we should frame the useful configuration options in use-cases.

Want to use Charles? Use setProxy().

Want to enable response caching? Here's the response cache implementation. Here's advice on choosing a cache size and directory on disk. 

Cookies? Here's the upsides and downsides. One problem with cookies today is we don't have a persistent cookie store, so you lose cookies when you relaunch the app.

Socket factory? Here's how you can prevent man-in-the-middle attacks from obnoxious governments that compromise CAs.