It will for release builds which don't re-use old packages but for existing chroots we could hardmask 9999 which would hopefully make the issue known. Maybe the simplest is after the first release that includes this change we can just suggest running setup_board --force to clean out the old stuff. This awkwardness is why live ebuilds should never be marked stable and used for local development only :)