Hey Patrick,
I'd certainly accept a PR that matches this functionality for ArrayList. The main reason that it hasn't happened is that the current implementation is very dependent on database queries. So it wouldn't be a small piece of work!
As a smaller change, it would probably be worth throwing a more useful error, e.g. "filter not implemented", if you tried to use filters that weren't there. This would also let us start implementing some of the filters, and leaving some of the less critical ones unimplemented. E.g. I don't know if I'd bother with FullTextFilter. This would make is easier to debug issues.
A similar gap probably exists with relationship traversal: I don't think $list->filter(['Relation.Field' => $value]) works. Again, I'd probably start by throwing clearer errors, and then implementing features one by one (I'd expect that a has_one traversal will be easier than a has_many)