OpenRC and systemd unit file interoperability in Artix Linux: Compatibility limits and conversion needs

The goal is to ascertain whether a native systemd unit file (.service) can be executed directly on an Artix Linux OpenRC installation that has the systemd‑compat package installed, or whether it must first be converted into an OpenRC runscript.

Artix provides systemd‑compat as a translation layer, but its coverage of systemd unit options is not fully documented. Features such as Type=notify, ExecStartPre/Post, complex dependency graphs, environment files, and certain logging directives may be unsupported or behave differently. This uncertainty affects start‑up ordering, failure handling, and log directory conventions, and it is unclear whether future Artix releases will expand or restrict this compatibility.

What specific systemd unit options are known to fail or require adaptation when used via systemd‑compat on OpenRC?
How does the compatibility layer affect service dependency resolution and start‑up sequencing compared to native systemd?
Is there a documented threshold of unit complexity beyond which conversion to an OpenRC runscript is strongly recommended?