I'm interested in what would you do in the situation I found myself.

The situation that happened with me recently - my Scrum team received 2 urgent and critical tickets from top management in the end of the sprint(3 days left), related to a feature that should have been announced in 2 days. For a better understanding - the feature is ready and working, but top management came up with 2 UI improvements that they want to see by the time of announcement. Those tickets don't match the sprint goal, I don't agree with their status of critical, but still, the request is to do them asap. 

In order to complete them we'd have to stop working on some remaining tickets, and still, the critical tickets wouldn't be ready by Sprint Review meeting. So accepting working on them would ruin the Sprint.

In order to prevent ruining the Sprint, I suggested 3 possible options:
1) Work on the tickets in the scope of the next sprint in 3 days and release UI changes after the feature is announced.
2) Cancel the current sprint and plan the next one with the critical tickets, but this means a 1-day delay;
3) Assign the tickets to another Scrum team that works with the same product and has their sprint just started. The problem is that they are not that familiar with the feature, so they wouldn't do tickets as fast as my team.

All 3 suggestions were refused, and the request remained unchanged - my team had to work on the tickets + I was called not flexible.

So guys, if you were in the same situation, what would you do? Agreed with the request, stand for one of the suggested options, or maybe you have other ideas?

Looking forward to reading your ideas and advice.