Please confirm that this issue appeared when you were testing the new architecture variants.
It is possible, thanks @ogra for pointing me in the right direction, that there are integration bugs with command-not-found and possibly other scripts.
You might want to consider filing a bug report to help with this because this seems to be a special case related to that new architecture.
In other words, we would not normally recommend deactivating the command-not-found configuration.