I'm sensing already this might lead to wilder gyrations in the non-conflicted MFs. The same is true for CW and War, as well as Elections, I believe. I didn't take part in the Beta. While the conflicted pair of MFs remain with static INF (today I did see a pair slip from a tied 9.8% to 9.7% each on the SysMap, so roundings might still factor), any other non-conflicted MFs have to absorb the remaining change, to allow a system's total INF to still add to 100.0%.
Take a four MF system. With two MFs in conflict, any actions to raise the INF of one of the remaining two can only create a decrease for the fourth MF, whereas outside a Conflict state, boosting just one MF might lead to a decline in INF for the other three, spreading the effect of the INF drop. This will need some testing and playing around with, but the 'dead weight' or INF anchoring of the pair of conflicted MFs needs some consideration. Conflicts now last seven ticks/days I believe, so we won't know for another ~5 days what the final INF levels are once these earliest conflicts resolve.
Unrelated to the OP, but the couple of conflicts I've observed post 3.3 matched INF on one tick and were conflicted on the next, i.e. a one-tick pending window. This might be a legacy effect of the cut-over between releases, so I'll be interested how it settles down over the next few days.