How can Joplin Portable trust an internal CA without modifying Windows certificates?

Hello,
I'm investigating a corporate use case involving Joplin Portable and WebDAV synchronization.
I have a WebDAV server hosted on my own infrastructure and everything works correctly on mobile devices. However, in some corporate environments, users cannot modify the Windows certificate store or install additional certificates.
My goal is to understand the best architectural approach for allowing Joplin Portable to trust an internal/corporate Certificate Authority (CA) without requiring changes to the Windows certificate store.
I am not asking someone to create a fork for me. Instead, I would like guidance on the most appropriate place in the Joplin/Electron codebase to:

  • Add support for a custom CA bundle;
  • Include a corporate CA certificate in a portable build;
  • Customize SSL/TLS validation for WebDAV synchronization;
  • Or implement another secure approach for trusting an internal CA.
    I have already started setting up a development environment and compiling Joplin from source, but before going further I would appreciate advice from developers familiar with Joplin's synchronization and Electron networking layers.
    Any guidance on the relevant modules, files, or architectural considerations would be greatly appreciated.
    Thank you.