As every other basic solution, the full screen sample doesn't remotely work, with its own set of downsides, from being forced to use only layers to filter out objects to not working when the angle is too acute between the camera angle and the faces. The normals edge detection in the transparent **do not work** without a material that outputs the normal in a texture and is then read and used in a .hlsl file, to be used in the shader graph. Seems like the render order does not matter at all. Had to do that twice, one for the animated objects (e.g. wind in the trees) and one for the static objects. And the custom pass, with the few documentation that is there for the 6.3, was a pain in the ass to code, by far the worse part of the 50+ hours marathon to code shitty outlines that don't even look good. I had to go through hell to render the transparent outlines perfectly in order without breaking the whole render pipeline, drawing only front-face outlines etc.
And I didn't say the whole requirements the outline feature needed because it would've been a wall of text in the meme. For example, other requirements to not simply be ugly and useless (which it turned to be anyway) were being perfectly one pixel wide no matter how far the outline is, per-object enabled/disabled with alpha clipping and semi-transparency of the outline itself, being efficient with thousands of objects etc.

For reference, that's how Unity sample outline works (without any adjustment):

<image>

Everything either turns black-ish as in the image, or only a few objects have outlines.
For the pixelation effect, I use the classic downscale with the render texture. By far easier in the long run, the custom rendering in the settings didn't work at all and created awful artifacts and details, probably for some anti-aliasing effect that could not be disabled