If you use one of the predefined workflows, you should get an image where you can get an idea of what needs to be done. But darktable doesn’t even aim at providing a jpg look-alike with any of the default settings.
One argument is that if you want the camera jpeg, you’re better off using the camera jpeg.
A (better) reason is that it’s virtually impossible to mimic the in-camera processing for all the different makes and models out there (every brand has its own internal algorithms to convert sensor readings in a jpeg image).
If with “presets” you mean camera styles and such, no, darktable cannot use those (again, the processing for such camera styles is unknown). Even though the styles and parameters are stored in the raw metadata, they cannot be used.
For the copy and paste of the history stack, you may want to read the relevant section of the manual as there are a few sublties involved.
@123sg : Just a nit, but the licence you linked to is not CC0. That would be equivalent to public domain. The link refers to cc-by-sa, but the others should be fine as well (for here, you’ll want to avoid the “nd” clause for e.g. play-raws)