head to head
Neither is harder. They score identically on all four axes, so the difference between them is in kind, not degree.

Optimization · Pure Optimization
Engineering unit pairings and reclass paths to dominate maps whose enemy scripts are fully mappable.

Optimization · Pure Optimization
Optimizing pair-up chains and offspring builds to steamroll deterministically scripted maps.
Fire Emblem: Awakening leans Optimization (Pure Optimization); Fire Emblem Fates leans Optimization (Pure Optimization).
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem: Awakening
No twitch elements; pair-up placement is the only spatial decision under time
Fire Emblem Fates
Turn-based menu play; no hand-speed demands
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem: Awakening
Enemies follow simple aggro patterns on fixed maps
Fire Emblem Fates
AI follows scripted attack priorities, not player modeling
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem: Awakening
Hit and crit rates plus random level-up stats create run variance
Fire Emblem Fates
Dual-strike/guard procs and hit rates inject meaningful RNG
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Fire Emblem: Awakening
Marriage pairings and Second Seal reclass chains are the optimization spine
Fire Emblem Fates
Offspring seals, asset/flaw selection, and supports are deeply planned
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.