Codebases need to allow adding new stuff, or changing old stuff, otherwise the project is frozen and the product cannot be developed further.
And code reviews rely on the fact that both developer and reviewer can read and understand the code. If the developer can use the code to invent a completely new language, it will be difficult to review its correctness. The job of the reviewer is to review the code, not learn a new language I just came up with.
And since we are not using Lisp we don't have a problem with it nor do we blame it for anything ;-)
Macro isn't your entire product. Loop macro is a thing since 1990's, yet it hasn't changed and everyone is fine with that. Macro can be extensible BTW, look at iterate macro in Common Lisp as an example.
You don't have to accept the code if you are worry about maintainability. But rejecting macro altogether is stupid.
>since we are not using Lisp
I know since you just invent imaginary problem and farm those internet points.
Seems like your problem tbh.