filmic (which is not like some Instagram-filter but a tone mapping operator) is applied because in preferences → processing → auto-apply pixel workflow defaults the option scene-referred is selected. You may want to set that to none, but, as @afre said, most people will use a display-referred (used in most raw processors, relies on base curve) or scene-referred workflow. For the differences, see this recent post by @anon41087856. Most darktable users on this forum use scene-referred nowadays, I think.
For the others, you can create auto-applied presets, where you first disable the module, and save that disabled state as a preset, marking it to be applied automatically.
However, you’ll probably want to keep white balance (without that, your images will look green - it is the module responsible for applying the camera’s white balance setting).
You’ll probably also want to keep exposure enabled, as, at least with the scene-referred flow, most images need an exposure boost. The reason is that unlike base curves (display-referred, also applied in-camera), filmic does not brighten the image: it keeps midtones fixed.
For an image as low-contrast as what you posted above, you can get away without a tone mapping operator, but for a high-contrast landscape, you cannot.
You’ll probably want to keep orientation, too, as that makes sure that portrait-mode shots are properly rotated.
Note that raw processors discussed here will give you the flat looking, straight-from-sensor image if you disable all optional tools / modules. They don’t do what many commercial tools do: they don’t default to a ‘camera look’. Read:
https://rawpedia.rawtherapee.com/Editor#Eek.21_My_Raw_Photo_Looks_Different_than_the_Camera_JPEG