First word of caution, if you are on Windows or linux you will need to paid version of resolve to open those files. Mac free will work fine.
I support minimum sharpening and NR in camera. This is always a one way street, and best done in post.
Saturation if not 'excessive' is less of an concern, you can back it off in post. Especially since there is no way that camera is going to exceed the capacity of REC2020 color space.
If you like the way -3 looks, go for it. If setting it to 0 makes less work in resolve, do that.
Darren Mostyn is my go to guide on resolve color management youtu.be/c4AVwVdKTHc?si=im_wS-l5K6FJoj-a
If your intention is to Monitor and Deliver a REC2100 HDR file to YT, this is not a trivial process. Up until recently a separate IO device was needed for Resolve to display HDR. This changed, but I haven't seen the process discussed (I don't own an HDR monitor myself). So some homework here will be needed.
Getting YT to recognize your exported files as HDR is also sometimes buggy. Exporting a Prores 422 file and checking its metadata with MediaTool is my recommendation.
YT details the metadata requirements here
https://support.google.com/youtube/answer/7126552?hl=enDo expect these files to look horrible for a viewer on an SDR screen. You can provide YT a bespoke SDR conversion LUT, but otherwise you are just rolling the dice with whatever tone mapping they choose.
Capturing in HDR or LOG and delivering to REC709 is certainly a much more common workflow and will remove a bunch of the pitfalls I mentioned. And what I would recommend for a beginner.