Longest and Shortest won't work in ReplaceList?

To me this is an interesting problem, however I think the question is a misguided one.

Briefly: Longest and Shortest only change the order in which an expression is searched for a match. They are not filters that eliminate potential matches.

As noted in the documentation:

If no explicit Shortest or Longest is given, ordinary expression patterns are normally effectively assumed to be Shortest[p], while string patterns are assumed to be Longest[p].

If several Shortest objects occur in the same expression, those that appear first are given higher priority to match shortest sequences.

If several Longest objects occur in the same expression, those that appear first are given higher priority to match longest sequences.

Realize then that all patterns already have a length priority as established by their type and position.

For example this always gives the same output:

Replace[{1, 2, 3, Pi, 4.4, 1/5}, {a__Integer, b__?NumericQ} :> {{a}, {b}}]
{{1}, {2, 3, π, 4.4, 1/5}}

This pattern is the same as {Shortest[a__Integer], Shortest[b__?NumericQ]}. The priorities determine the order in which different alignments are tried and the first match is returned. This process is always the same therefore the result is always the same. Using a different length priority results in a different search order and (possibly) a different match but it is always deterministic.

So what happens when we use ReplaceList? The same priorities are respected but now the pattern engine keeps looking for matches rather than stopping with the first one found, and all matches are returned in the order searched. Compare these outputs:

expr = {1, 2, 3, Pi, 4.4, 1/5};

ReplaceList[expr, {a__Integer, b__?NumericQ} :> {{a}, {b}}]

ReplaceList[expr, {Longest[a__Integer], b__?NumericQ} :> {{a}, {b}}]
{{{1}, {2, 3, π, 4.4, 1/5}}, {{1, 2}, {3, π, 4.4, 1/5}}, {{1, 2, 3}, {π, 4.4, 1/5}}}

{{{1, 2, 3}, {π, 4.4, 1/5}}, {{1, 2}, {3, π, 4.4, 1/5}}, {{1}, {2, 3, π, 4.4, 1/5}}}

Note that Longest is not ignored; it changes the search order, as it always does.

While the order is different the set of matches is the same; it has to be because the same input expression and the same patterns are used in each case. All that changes is the order in which the alignments are checked.

To illustrate this in different way without ReplaceList we can use a failed condition to echo back matching alignments.

expr /. {a__Integer, b__?NumericQ} /; Print[{a}, " ", {b}] -> Null;

{1} {2,3,π,4.4,1/5}

{1,2} {3,π,4.4,1/5}

{1,2,3} {π,4.4,1/5}

expr /. {Longest[a__Integer], b__?NumericQ} /; Print[{a}, " ", {b}] -> Null;

{1,2,3} {π,4.4,1/5}

{1,2} {3,π,4.4,1/5}

{1} {2,3,π,4.4,1/5}


As a workaround, you can use Select to filter down the results of ReplaceList to the set you want by using MatchQ and SequencePosition.

v = {5, 1, 2, 1, 2, 1, 2, 1, 2, 4, 3, 3, 3, 3, 3, 3, 10};
rl = ReplaceList[v, {Shortest[pre___, 3], 
    Longest[Repeated[Shortest[rep__, 1], {2, Infinity}]], 
    Shortest[inc___, 2]} :> {{pre}, {rep}, {inc}}];

Then

Select[
 Not[MatchQ[#[[2]], {Repeated[x__, {2, Infinity}]}]] &&
 Max@Flatten@SequencePosition[#[[1]], #[[2]]] != Length@#[[1]] && 
 Min@Flatten@SequencePosition[#[[3]], #[[2]]] != 1 &
]@rl

(*
{{{5}, {1, 2}, {4, 3, 3, 3, 3, 3, 3, 10}}, 
 {{5, 1}, {2, 1}, {2, 4, 3, 3, 3, 3, 3, 3, 10}},
 {{5, 1, 2, 1, 2, 1, 2, 1, 2, 4}, {3}, {10}}}
*)

The ReplaceList cases of interest are those with no repeated sequences in rep__, have pre___ that does not end in rep__'s pattern, and have inc___ that does not begin in rep__'s pattern. Note that a third possible match has been found that was not initially considered by eye.

Hope this helps.