This was all dancing around another missing "rung" in the "LIFT_BYTE() ladder"...
Having the slots be "antiform" PARAMETER! wasn't really buying that much, because antiforms were still "the kind of thing you could get as a product of evaluation".
As my example shows about "asking if something is an integer", if the antiform byte didn't kick the parameter out of consideration for that question, being an antiform wasn't helping much at all!
Hence a "HOLE" has to be a BEDROCK_0 state (or "dual state").
And one of the great things about being a dual state is that it gets to choose what it acts like when you try to access it like a value. NULL is a great choice, because it means when you do a MAKE FRAME! and get a bunch of "holes" (bedrock PARAMETER!s), it looks to a casual observer like it's a bunch of nulls. Hence DEFAULT and such will just overwrite them.
(NULL turns out to be the superior choice to VOID!, now that pushing things to the edge of in-band representation is no longer necessary, due to holes being out of band. )
This exemption is no longer applicable, as TRASH! is unstable now... and there's no reason for it to be an exception!