BetaFlight and CleanFlight have been flinging poo at each other for years.
Unless they are a really good pilot, most people probably won't see the difference. Do you care if you use Windows or Linux to send a message? Most people don't think about it. They grab what they find convenient and send the message. People who give a dang about it probably aren't much fun at parties.
They flash the same because at the core, they are the same. BetaFlight is what was created when a split inside the ranks of CleanFlight happened. Follow the instructions. Wear a wrist strap when handing your FCB. Don't drink a soda on the workbench next to your FCB while flashing... you get the idea.
As I understand from your description, the latest version of BetaFlight is buggy but an earlier version of BetaFlight worked. If this is accurate, I recommend reverting BetaFlight to an earlier version of BetaFlight. I think you will find it simpler to adjust to such a reversion than flipping to CleanFlight.
During the flashing process (again, follow the instructions), choose an earlier ROM for your board.
I had a Naze32 rev 5 that I ran BaseFlight, upgraded to Cleanflight, then upgraded to BetaFlight and finally to dRonin. So long as you aren't running DJI hardware, it's your motherboard. Run whatever ROM you like.
Fork it! Make your own ROM.
But be warned.
You mention limited experience. Flashing your ROM may wipe out your settings. Changing ROMs will introduce you to different interfaces completely. You won't have limited experience when you are tweaking your settings on your 4th ROM for the 27th time. You'll be a salty, veteran.
In other words, if the copter flies well, just fly it. You'll have more fun at parties.