Chains of emancipation + rotblood promise, warding flasks and timetwist interactions are bugged

Chains of emancipation should give max rage if you pop a warding flask giving curse immunity while cursed from rotblood promise, this is not happening at the moment, the warding flask is not giving immunity and removing the curse.

I know this should technically work because it used to happen, you can see this interaction in this fast af video https://www.youtube.com/watch?v=MAueqsr18yU

Also equipping the timetwist ring while rotblood curse is active is giving max rage, this also should not happen. Timetwist description states unaffected by temporal chains not immunity, i should still be cursed but unaffected.

The timetwist ring giving immunity is also preventing the max rage gain from reaching 25 rage from chains of emancipation. You reach 26 and the temporal goes away, but you do not gain max rage, if you unequip the timetwist and reach 26 rage you gain max rage.

Tl;Dr: flask of warding is not giving immunity and timetwist is giving immunity instead of unaffected contrary to its description.

I made a mistake i thought the warding flask also was supposed to give 4s immunity like bleeding and freeze, but it's the exception and it doesn't give immunity, so the flask may be as intended.

The timetwist interaction however i still think it's a bug, it should not give max rage on equip or prevent the max rage gain from chains since it's not supposed to give immunity.

Just jumping in here to report that I'm also seeing the same behavior.

The wording of 'Removes curses on use' I would think would still remove permanent curses and then reapply them immediately, still causing Chains of emancipation to give max rage.

Can we get some clarification from GGG if this is intended vs. a bug?

I'm having this problem as well - was trying to duplicate a build someone was using last league before the flask nerf but the chains of emancipation seems to not work now at all with the new flasks... Would be nice if it could be fixed or at least addressed as intended. Sucks when GGG kills off some build-enabling uniques like this that take a lot of investment to work anyways.