The key thing is that you need to meddle with the emulator to turn it into a Retroarch core, and the newer the console, the more likely it is to not map nicely onto the interface and need invasive modifications that break things. If that leads to a bunch of support threads blaming the main project for Retroarch-induced problems, that can be irritating, especially if people aren't polite about it or bury the lede by failing to mention they're using Retroarch. If it happens enough to be a problem, then obviously the upstream project's community isn't going to remain welcoming.
As for the name change, if you're forking a GPL project (which you have to if you're turning it into a Retroarch core), you're required to publish it under another name or the original name with your name added so it can be easily distinguished from the original and the original creator doesn't catch flak for your bugs.
As for the name change, if you're forking a GPL project (which you have to if you're turning it into a Retroarch core), you're required to publish it under another name or the original name with your name added so it can be easily distinguished from the original and the original creator doesn't catch flak for your bugs.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X
RAM: 16GB
GPU: Radeon Vega 56
CPU: AMD Ryzen 5900X
RAM: 16GB
GPU: Radeon Vega 56