No, you don't.
The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
I'd use dcdiag / repadmin tools to verify health
correcting all errors found before starting
any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to
Accept as answer if the reply is helpful--
I've been reading about the best method to upgrade/migrate the 2008R2 DC, I have done the migration in a test lap environment directly to 2019 DC and worked with no problems, but did not test the in-place method yet, I guess the second method requires a 2012R2 upgrade first then go up till you reach the required server version
Why it is not preferable to do an in-place upgrade for a DC server?
risk, corruption carry forward.