Pijul is a product that seeks adoption. I'm a customer. Pitch.
Pijul fails to present me any reason or example for its superiority to the status quo, Git. It only provides vague points like simply claiming to be more "correct". I need to know how my workflow will improve as a result of replacing Git with Pijul.
Sure, you might say that I'm not the target, but as a software developer running my own DevOps product and consultancy company, I don't find that to be the case.
For your specific counter-arguments:
1. Pointing out a corner-case pain point with Git, and simply stating that Pijul will be "correct" is not at all informative. Git has countless pain points, and so will Pijul have. What matters is the 90% experience, not the corner cases.
"A conflicting state is another valid state" does not mean anything to a user. The source is not in a valid state during conflict, and sharing invalid source is not interesting, so this falls under implementation details again.
Merges have pros and cons, which is why Git also has other mechanisms which the users can select, such as rebase.
Again, what one needs to know is how the workflow of a developer is affected, not how beautiful the internal structures may end up being.
2. Ah, a partial checkout and a partial clone differ, at least in Git terminology, which is the status quo at the current time.
However, what people care about is not the ability to perform a partial clone, but the speed of certain operations. If a full clone is fast, the user won't give a damn about partial clones.
Instead, what one should then put as a prominent feature is monorepo capability, and direct performance comparisons between Git and Pijul.
However, do note that Microsoft appears to handle monorepos in Git just fine with GVFS, through partial clones.
Also, the ability to reorder patches without changing their identifier will to many be an anti-feature which might render Pijul a no-go. From a user-perspective, Pijul and Git are both equally capable of reordering patches, Pijul just lacks the ability to easily and uniquely identify an entire tree state.