I think the answer to both questions is "sometimes", and most kernels go out of their way to avoid ever answering this question. They just don't want responsibility for it.
I don't agree these factors should be hidden, unless the API guarantees every single operation is atomic & durable.
Full details as to atomicity & durability need be available to callers (not just SQLite, but any application that wants to provide a reliable datastore) so that they can write information durably including across coordinated multi-file data structures.
Then they could at least say "we're doing everything we can; next time you buy a storage device look for feature X".