Adding any keyword is by definition breaking backwards compatibility, so I'd say this is the correct behavior.
For example, "goto" is a reserved word in Java, while not a keyword. Inversely, in Fortran, keywords are not reserved names, so `if if then then else else` is valid. C# has "keywords" and "contextual keywords", both categories being keywords, but only the former being reserved names.
Regardless, a builtin might be referring to a function that's included as part of the base language - like make() in Golang or zip() in Python.
EDIT: Since someone has gone through the trouble of downvoting this viewpoint, I would like an explanation as to why I'm wrong here. I cannot imagine a scenario in which doing so would not likely break existing code.
I think I must be misreading you, because it sounds like you're arguing for the idea that adding new names to an API should be considered a breaking change? I'll accept that maybe reflection will catch those changes, but with that exception why would any code even notice?
I already have a "filter" function defined in my program, so it will shadow the builtin function, and my program will still work as intended.