ZFS can even tolerate the loss of a SLOG device as long as A) the SLOG is not currently being read to rebuild after a crash and B) all writes that occurred before the SLOG was lost have been fully flushed to the pool disks.
Just expect a hit on performance if your workload leans heavily on the L2ARC. Also, in my experience, L2ARC is a lot less useful than a lot of people think; doing some workload characterisation is an interesting and informative exercise.
As an aside: an SLOG is usually useful. Unless your workload is effectively read-only, a SLOG can make a pool perform close to SSD levels for most workloads on the cheap. Just be careful to get a quality SSD for the SLOG.
OT: Anyone seen behaviour like this? https://lists.freebsd.org/pipermail/freebsd-net/2016-Februar...
All you're really losing is the caching, which may not be so important for what is going to be mostly writes in this backup app.
If you want to add some cache headroom to a Pi, you could add a USB stick to the pool as cache. I just threw RAM at my homebuilt NAS, so I can't say how helpful this is. I imagine it's useless for sequential and pretty good for small random access reads, directories etc.