hey @duke22
I was following the development of community project in the past and what was really bothering me was not the project itself, but the constant changes into the UE API that required quite constantly each new release to make a lot of changes. A blueprint version in case gives a little less headache, while I agree the matter about performance, once the blueprint nativization came out, for the assets where it works, it is a bless. Projects like PWS benefit from nativization because buoyancy in plain blueprint really does not perform well, and for me community project does it right while placing anything about buoyancy inside the C++ code. I don’t recall the source correctly, but I remember I have stripped in the past everything but buoyancy, because the other features I was not confortable leaving because thats more code to maintain, I didn’t need them and I didn’t regreat… those features thou could be placed in a separate plugin for the sake of portability and isolation: ie: why the code does not works in new release? Oh it is the fish manager, but oh I dont use it 
The quality of is good enough for most projects and I think anyone wanting to use it, should learn from it, and MUST strip anything he thinks doesn’t need to be there to seek performance, mainly the Ultra which has few things that can be changed. I don’t have budget to look at it right now or I would contribute for it, but that might change in the future (soon (TM from someone)).
It is good and I congratulate engaged into project.