In the last few hours, I've been thinking about how much effort would it really be to fork it, Iceweasel style, and IMO even just forking, renaming would be a pretty significant effort (if done right).
Fork the web page, you cannot just replace Rust with ALTERNATIVE, because ALTERNATIVE is not used at npm, you don't have a Discord community, and you don't have books and videos, and no foundation. All those changes would need to be kept up-to-date.
You could also have a new file type, .altrs, while you still want to be able to use Rust's files. Same goes for tooling, supporting websites such as crates.io: you might want your own, but you also want all the tools to work with the Rust crates. With the new file type, you need people to know how to change their config to treat .altrs files as regular .rs files.
.. though I don't know how much of it would be really necessary if all you want is to not violate their new policy, so it's more of a thought experiment at this point.
Fork the web page, you cannot just replace Rust with ALTERNATIVE, because ALTERNATIVE is not used at npm, you don't have a Discord community, and you don't have books and videos, and no foundation. All those changes would need to be kept up-to-date.
You could also have a new file type, .altrs, while you still want to be able to use Rust's files. Same goes for tooling, supporting websites such as crates.io: you might want your own, but you also want all the tools to work with the Rust crates. With the new file type, you need people to know how to change their config to treat .altrs files as regular .rs files.
.. though I don't know how much of it would be really necessary if all you want is to not violate their new policy, so it's more of a thought experiment at this point.