If an organization did this, I'd be all for it. An individual? I'd bet this is going to slow down updates to Chromium significantly, and eventually lead to either security issues or maintenance fatigue resulting in closure of the project.
I'm not saying it's 100% going to happen like that, but that's on the wrong side of my risk tolerance line for adding a tool to my everyday suite.
That tradeoff can be worth it, but all I'm getting out of it here is reduced application footprint? I'd rather use the bloated tools or wait for someone with deeper pockets to make a less bloated tool. Or a similarly small project that writes it natively.
If that concerns you, though (or if the author really did outright fork Chromium), it looks like it runs in an ordinary browser, too (e.g. via postwoman.io or localhost:3000).
> the author stripped down Chromium for the UI
If it's just CEF then I feel like that wording is misleading.