You don't need to reply to this message, just save it as a suggestion.

Last year I mentioned this to Sanidhya Singh in a private mail message.  
It's about this change:

  https://gitlab.com/inkscape/inkscape/-/merge_requests/5169

Any time a newbie user get scared about an error message you'll agree
to change things?

That error message was not a bug but a useful feature.  Half of the
times the directory paths that Inkscape keeps in its config file might
not even exist anymore.  It's acceptable (to a certain extent) for an
application to create, without prompting, an entire directory tree in
directories intended for configuration (e.g., ~/.config) or temporary
files (e.g. /tmp), but not in directories intended for the user (e.g.,
~/Documents).  The sensible thing to do would be to either revert this
change or, at least, warn that directories will be created when the path
saved in the export dialog memory doesn't exist.

By the way, an example of when the error message is an error:

  $ inkscape new.svg

  ** (org.inkscape.Inkscape:57301): WARNING **: 14:02:38.913: Can't open file: /home/<user>/new.svg (doesn't exist)

  ** (org.inkscape.Inkscape:57301): WARNING **: 14:02:38.916: Can't open file: /home/<user>/new.svg (doesn't exist)
  ink_file_open: '/home/<user>/new.svg' cannot be opened!
  InkscapeApplication::document_open: Failed to open: /home/<user>/new.svg
  ConcreteInkscapeApplication::on_open: failed to create document!


This shouldn't happen, since the user is deliveratly trying to create a
new document in the current directory.

The fora are mostly user to user assistance.

Maybe share your thoughts publicly with the developers here: https://gitlab.com/inkscape/inbox/-/issues/10283