Hi soner peker,
Thank you for laying out the exact call configuration and separating documented behavior from runtime observations so clearly. Since you are looking for documentation rather than test results, I have gathered the relevant passages from the Microsoft documentation for each of your questions, together with the points these pages do not address.
The NtCreateFile function (winternl.h) page describes ObjectAttributes.Attributes as a value that "can be zero or OBJ_CASE_INSENSITIVE". The OBJECT_ATTRIBUTES structure (ntdef.h) page lists OBJ_DONT_REPARSE among the flags the Attributes member can contain, and its Remarks give ZwCreateFile and ZwCreateDirectoryObject as examples of routines that accept the structure. Neither page states whether the NtCreateFile wording is an exhaustive list, and the OBJECT_ATTRIBUTES page does not mention user-mode NtCreateFile.
On the leaf component, the OBJ_DONT_REPARSE entry states that no reparse points will be followed when parsing the name of the associated object, that the attempt will fail and return STATUS_REPARSE_POINT_ENCOUNTERED if any reparses are encountered, and that the flag can be used to determine whether there are reparse points in the object's path in security scenarios. The entry does not specifically mention the final path component, RootDirectory relative names, or a single-component ObjectName.
The NtCreateFile Remarks state that if FILE_OPEN_REPARSE_POINT is not specified, normal reparse point processing occurs for the file. The same page lists the CreateOptions flags compatible with FILE_DIRECTORY_FILE as FILE_SYNCHRONOUS_IO_ALERT, FILE_SYNCHRONOUS_IO_NONALERT, FILE_WRITE_THROUGH, FILE_OPEN_FOR_BACKUP_INTENT, and FILE_OPEN_BY_FILE_ID. Neither NtCreateFile nor OBJECT_ATTRIBUTES describes how OBJ_DONT_REPARSE interacts with that normal reparse processing.
As for the result and applicability, STATUS_REPARSE_POINT_ENCOUNTERED is the status named in the OBJ_DONT_REPARSE entry. The OBJECT_ATTRIBUTES page does not list Windows version requirements, filesystem restrictions, exceptions, or alternative statuses for this flag. The ZwCreateFile function (wdm.h) page notes that, for calls from kernel-mode drivers, the NtXxx and ZwXxx versions of a routine can behave differently in the way they handle and interpret input parameters. None of these pages describes differences between user-mode and kernel-mode callers for this specific flag.
For the points these pages do not cover, a confirmation of the supported contract would need to come from the Windows product team, which is outside what Microsoft Q&A can provide. You can open a case through Windows Developer Support and include the exact call configuration and the four questions from your post. You can also use the Feedback option at the bottom of the NtCreateFile page to request clarification of the Attributes description.
I hope these documentation references and the information above help clarify what the published guidance currently covers. And if you feel the information has helped you move forward, you are welcome to follow this guide when convenient, as it can help others with similar Windows and SQLite resource lifetime questions see what worked for you. If any of these passages read differently from your understanding, feel free to share it here and I will take another look.
Thank you.