You may want to consider using +current instead of and/or in addition to -tie, but that said, I don't think that will actually work today.
"current - By default Maximizer considers your current equipment in Hardcore and Ronin. With -current keyword it does not, with +current keyword in aftercore it forces it to be considered. Not considering current equipment will reduce the number of combinations considered, but will sometimes mean changes of equipment are suggested even though they don't improve what you are wearing."
(This specific example is weird because there's no reason to run maximization when you just want to equip a specific outfit but not affect anything else.)
This is controlled by the hardcoded tiebreaker in MaximizerSpeculation.compareTo and cannot be overridden otherwise -- in particular, it's preferring items that drop items / meat.
(In its entirety, in order: prefer success, higher score, lower B count in Bees Hate You, item droppers, meat droppers, tiebreaker unless -tie is used, rollover effects, unbreakables, gear that's already equipped if it's considered)
It might make sense to inline these additional modifiers into the tiebreaker expression (in Evaluator.java), but that would require adding handling of "optional" boolean modifiers. We could also change "Drops Items" and "Drops Meat" to be numeric modifiers (which would be more flexible, although it could break some weird existing workflows).