Nothing is solved, even with the update you cannot modify Rust and remove parts as we need to do it. So answering your questions:

How does this change affect the legit evaluation of Rust?
No change within as Rust stays on being not compatible with strict freedom and principle oriented onto.

Does the wiki need an update?
No as there is the no real change.

Or is the Rust problem even solved now, opening the door to RUST usage without wrecking freedom?
See above.

What about Cargo?
That is one further issue as we cannot remove it and would need again a more free and permissive licensed fork to do that. When something has a guideline for logo and more policies for media, we should stay for sure critical. When we remove Cargo and modify Rust as package at the points needed we would nevertheless ask again for "permission" and so the points mentioned stay again: Rust is NOT free software. It is just in some way made compatible for a free distribution without modifications. The modified guidelines give more safety for the pragmatic approach. But Hyperbola is not oriented onto pragmatism. Other systems can do as they want for sure.

Does the change give reason to keep or change hyperbolas stance towards RUST?
We don't have any further interest to include Rust as it is not only that point. You need even more parts to compile applications. So the toolchain is right away very complex and we don't have also interest into bloated and complex tools.

If the change makes a change of hyperbola's policy reasonable, how would that change hyperbola project development?
See above: We don't and won't integrate Rust or tools based onto that at any point in the future. We also have no interest into Rust in a whole. It's toolchain is bloated right from the roots, not only the compiler is needed for many applications and we have not talked about non-free libraries being nevertheless needed at a point to be downloaded for building - that's the reasoning we have only ONE package-management and nothing more like pip for Python or others.

Also Rust is included with "corporate interests", so we have another point to reject its integration. Nothing is changed and nothing will therefore be changed for Hyperbola. We go for free and libre soft- / hardware. Besides that hardware is another point: Software is made by people for people, with the community in mind and to share free culture and information. Not about corporate interests and there is for sure no point we will go for that point. And to underline comparisons like LibreOffice would have comparable guidelines (mentioned within the link from the Trisquel-forums): We cannot compare a single application with a complete programming-language and its toolchain behind.

A personal note
I find it interesting that people discuss ABOUT Hyperbola instead talking here WITH us. I can only renew the invitation being made as those discussions will never lead to a better understanding otherwise. Nobody is enforced to follow our perspectives here, we just ask for pure friendly tolerance, nothing more and nothing less. But that's a good example why so-called modern communication has a malfunction: People talk more about each other instead with each other. Cannot change that, but as said: Would be cool to do it other way. And also to note: It would be good if we end discussions about Rust for the time being now. All was and is said now. When there is another clue and part of the team have found a way, well there is a chance for discussing again. But for now? Nothing in reach. And if the people elsewhere want to discuss, the invitation stands for a long time.

Hyperbola is a small system with a small team: So for sure we have to wait. And personal: Looking into gcc-rust as it is comparable to the same problems back. The GO-language and its official release with alone technical issues and now the official Rust with its for sure different base of licensing-problems, but nevertheless also bloated toolchain. When we do that we would for sure have further issues. So better to leave those grounds and focus onto our roadmap.

Besides: Rust is and stays corporate open-source, NOT free and libre software with free, libre and permissive licensing.
We would make a foul compromise when integrating that.

Absolutely! Let's hope the law-problems can be sorted out and there is a gcc-rust will get in the making. Surely that is a chance in the future without having those problems and including lightweight tools. That would be a fine compromise in the clear lookout. But until: HyperbolaBSD will be our goal and therefore beyond also.