On 1, I would just stick to standard TCP, unless you have a specific requirement for the optimized profiles. It's trivial to switch between those optimized profiles, so you could just evaluate them, since this is a new setup. In my experience, those don't add much to a standard web app and the "fast" profiles can limit some capabilities. OneConnect does more to improve performance than anything I've evaluated, especially with https.
On 2 300 seconds is a standard timeout setting. If you have some application that takes a long time to return a result (I've seen a lot of reporting applications that can be like that) you might need to increase it, but I would only do that on an as needed basis as you could impact performance of the entire unit if you have too many open connections.