Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.
If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.
I have used both Arch and Eos. I use a special tiling wm, and I have Nvidia. Form Arch I have to install everything I need, from Eos I just select install without a wm/dm remove some bloat and install the missing. Almost the same outcome, almost the same time to set up. So it does not matter (for me).
Out of the box Eos provieds ease, Arch provides knowledge (along the way). I have friends which are tech savy enough to daily drive Eos, but unintrested to learn how the linux ecosystem works by installing Arch (at least until a bug forces them to read the wiki)