I understand what you are seeking. The issue is one of resources.
The file geodatabase API is based on the 10.x ArcObjects code to implement file geodatabases. It does not support multi-threading. Adding a great deal of trapping code (which was present in a different level of abstraction in ArcObjects) would alter the "Sergeant Friday" ("Just the code, ma'am, just the code") nature of the library, increasing size and decreasing performance, mostly to facilitate unsupported functionality. And in order to accomplish these changes, programmers would need to be taken off other (revenue-positive) development projects.
You can certainly submit requests for enhancements to the FGDB API through the Ideas site, but it doesn't seem likely that such enhancements would be adopted. Based on my observation of the process (which is not direct), it seems that enhancements to increase breadth of functionality (exposing existing geodtabase behavior) will be chosen over depth of functionality (error trapping for invalid pointers).
- V