Definitively, but it could work if was just one of the possible frontends and create another, for example, web based frontend.
That naturally adds quite a bit of complexity as you either need a central server app that holds the source of truth or handle merging otherwise, be it by let the user take care (e.g., holding it as somewhat merge friendly text records in git) or do come up with some automatic conflict resolution.
IMO that shows why developing and using such CLI tools is somewhat popular; it's really simple to do but often then only works for a single person or a team with a very similar mindset in the usage/tooling regard.
It's rather basic feature set; no sub-task support for example. But I do not know of any other way to sync tasks and calenders across a team where preferences for different clients and tools vary.
Unfortunately this breaks down rather quickly as the various calDAV and cardDAV implementations vary wildly for features outside of simple task lists. About a year ago I tried configuring sync between Linux/Windows/MacOS/Android and failed. I documented my search here [1].
1. https://stevenvanbael.com/open-calendar-task-space-is-a-mess
I think it is up to us OSS nerds to keep working towards a world that is more interoperable, preferring protocols over implementations. It is either that or giving up entirely and rolling over to the whims of Google, Meta and other big corps.
In the two minutes it took me to write this comment Google has released two new chat apps, fragmenting my contact list even more /s.
The thing that makes Kanban useful is the collaboration in a team. I doubt a whole team would agree to use this tool though.