Only do this if you've reproduced what seems to be a bug in one of the latest two releases, otherwise contact your distro.
The systemd github issue tracker is not a support forum, you'll find this stated in the issue submission form.
But on a normative level, perhaps a project that doesn’t want to support users shouldn’t have subsumed a huge swath of user land things?
It's not that the project doesn't want to support users in some absolute sense, it just doesn't want it happening in github issues.
The project provides the systemd-devel mailing list for that, but it's still preferred that users stuck on old versions determined by their distro's release cadence seek support from their distro vendor. It's likely such slow-moving distros are patching their LTS versions anyways, and are best positioned to support what they ship.
You may not like it, I'm just playing messenger here, to try save some bother on both sides of this subject. Use the mailing list for support questions, or contact your distro vendor for support.
You could also replace umount with a wrapper that logs the parent process tree on execution.
And of course you can open an issue on GitHub.