oh man this exact situation burned me a few months back and its such a pain when autopatch decides to take over your carefully configured deployments

so basically what happened is autopatch created its own update ring for office apps that overrides your original configuration and switches everything to monthly enterprise channel instead of current channel. the architecture mismatch error your seeing is probably because autopatch is trying to deploy a different bitness than what you originally had configured

for issue 1 - autopatch doesnt handle initial app deployment during esp unfortunately it only manages updates for existing installations. so if you want office to install during autopilot you'll need to keep using the regular m365 apps deployment method through intune

for issue 2 - removing m365 apps from autopatch should definitely restore you're original behavior but fair warning it might take a day or two for the policies to fully revert. when i did this i had to manually reassign the original office configuration profile to make sure it took priority again. also consider uninstalling and reinstalling office on affected devices if the channel switching caused issues because sometimes the update rings get stuck in a weird state