I didn't think it would, and the reason I didn't even suggest it. Nevertheless, Apple Support is probably going to have you do that anyway, so now you can tell them you did already and it didn't help.
Another idea is to create a new, temporary User Account and determine if you can duplicate the problem while logged in to that Account. It's almost certain the problem will not manifest in that Account, but that determination won't help fix your usual Account. The solution you proposed (erasing the Mac and migrating content from the iMac) is more likely to be successful.
Also likely to be successful, but much more time-consuming, is dragging the entire Safari User Library to the Desktop, followed by methodically dragging components back into it and testing, then repeating until you find the guilty party. I would prefer a more targeted approach, but I would also need to devote the better part of a day to find the exact file or files that need to be fixed or trashed. Perhaps Apple will come up with a faster solution.