Comment # 13 on bug 1165780 from Franck Bui

(In reply to Fabian Vogt from comment #10)
> AFAICT it moves the PID reloading to happen only after local-fs.target,
> which mitigates bug 1137373. It's mostly for symmetry to
> btrfsmaintenance-refresh.service, which already has After=local-fs.service.

Since both units (.path and .service) have the default dependencies both units
don't need "After=local-fs.service" as it's already implied.

> It still reloads systemd at least three times during boot and when sysconfig
> changes.

This is what should be optimized IMHO.

That said the idea of automatically (re)starting a unit if a config file was
changed is disputable, assuming it's the purpose of
btrfsmaintenance-refresh.path. IMHO reloading a new config should be done
explicitly like it's always been the case, and who knows the state of the
contents of the config file when sysadmin is saving it.