When it's a choice between making it easier to import changes or harder to import bugs, I know which one I think is more important when dealing with a security library.
Put another way, if you forked because upstream was crap, not changing because it makes it easier to accept upstream patches is a poor reason not to change something that might benefit from it.
That said, the relatively poor history of OpenSSL and the relatively high quality of software that comes out of the OpenBSD project leads me to think I know what the likely outcome of refactoring code is in this particular scenario.
https://github.com/systemd/systemd/commit/61f33134fc9231e07e...
I'm all for blaming legacy but this is unfortunately still a trend.
BoringSSL doesn't use that style: https://boringssl.googlesource.com/boringssl/+/master/ssl/s3...
There's no need to revise the entire codebase either, just fix the lines you touch, and don't introduce new cases like in that commit.
LibreSSL didn't spring into existence out of whole cloth. It started as a fork of OpenSSL, which goes back to 1998.
The "questionable style" is from legacy code. It would be a massive effort to revise the entire codebase. And if LibreSSL did that, it would make it harder to import changes from OpenSSL and from other forks such as BoringSSL.