Lambda that uses INDEX with array arguments behaves inconsistently when saved in the Name Manager

I do most of my development work in v2606 and I've noticed it. From what I've tested in Beta/Insider channel, the quirk does not exist.

The common thread in testing seems to be this quirk exists for lookup/retrieval functions (e.g., INDEX, VLOOKUP, XLOOKUP, etc.) but does not surface for shaping/selection functions (TOCOL, CHOOSEROWS, SORT, FILTER, etc.). BTW - I would not include Excel for the web in Lambda tests because that version doesn't fully support Lambda (e.g. Element-to-Apply (ETA) evaluation) and doesn't always resolve AFE modules well.

// These results require coercion
TestAλ=
LAMBDA(
    array,
LET(
    arbit,INDEX(array,SEQUENCE(4),1),
    arbit
));

TestBλ=
LAMBDA(
    array,
LET(
    arbit,VLOOKUP(TAKE(array,,1),array,2,0),
    arbit
));

TestCλ=
LAMBDA(
    array,
LET(
    arbit,XLOOKUP(TAKE(array,,1),TAKE(array,,1),TAKE(array,,-1)),
    arbit
));

// These results do not require coercion
TestDλ=
LAMBDA(
    array,
    FILTER(array,SEQUENCE(ROWS(array)))
);


TestEλ=
LAMBDA(
    array,
    CHOOSEROWS(array,SEQUENCE(ROWS(array)))
);


TestFλ=
LAMBDA(
    array,
    SORT(array)
);


TestGλ=
LAMBDA(
    array,
    TAKE(array,3)
);


TestHλ=
LAMBDA(
    array,
    TOCOL(array)
);

TestIλ=
LAMBDA(
    array,
    CHOOSECOLS(array,SEQUENCE(COLUMNS(array)))
);

TestJλ=
LAMBDA(
    array,
    WRAPROWS(TOCOL(array),COLUMNS(array))
);