FWIW, I have no experience with Perlbrew. I don't see the point of it. I actually hate it - which is quite irrational (isn't all hatred ?) given that I've never tried it.
For mine, I just build perl in the normal way by running 'Configure', 'make test', 'make install' and finally 'make distclean' (in prepraration for the next build, of a different configuraton).

So, for my stock standard build of perl-5.42.0, I started with:
sh Configure -des -Dusethreads -Dusemultiplicity -Dprefix=/cygdrive/c/cygperl-5.42.0-d -Dlibpth=/lib/gcc/x86_64-pc-cygwin/11

For my -Duselongdouble build:
sh Configure -des -Dusethreads -Dusemultiplicity -Dprefix=/cygdrive/c/cygperl-5.42.0-ld -Dlibpth=/lib/gcc/x86_64-pc-cygwin/11 -Duselongdouble

And for my -Dusequadmath build:
sh Configure -des -Dusethreads -Dusemultiplicity -Dprefix=/cygdrive/c/cygperl-5.42.0-q -Dlibpth=/lib/gcc/x86_64-pc-cygwin/11 -Dusequadmath

I think I need that '-Dlibpth' switch only because I want the quadmath library to be automatically found for all 3 builds.
For you, I think that directive would end with "13" instead of "11", but I'm only guessing ... and it might even be the case that, with your gcc-13, there's no need for that directive any more.

I regularly hit a failing test in t/porting/exec-bit.t, and in one other file (I forget which).
My Cygwin installation is a few years old - your Cygwin might fare better.
Those couple of failures don't bother me at all, and I've not reported them.

I select which perl I want to use by running (eg):
export PATH=/cygdrive/c/cygperl-5.42.0-d/bin:$PATH

If I want to switch to a different perl I just run (eg):
export PATH=/cygdrive/c/cygperl-5.42.0-q/bin:$PATH

On cygwin I have (double, longdouble and quadmath builds) of perls 5.36.0, 5.38.0, 5.40.0, and 5.42.0.
It's easy to handle, and I'm not about to bother with perlbrew.
Of course, those who do want to use perlbrew for whatever purpose, are entitled to do so.

Cheers,
Rob