I just pushed a workaround that should hopefully fix the issue.
Thanks Ihor, it seems to work for me now! Before when I evaluated ~(org-matcher-time "<2022-08-15 Mon 00:00>")~ manually it would give me the error, however I don't have it anymore with the latest main branch.