Observations
The permission tab that the OP sees actually shows some missing permissions:

Verifying the permissions of the OP result file using Adobe Acrobat, however, there is another result:

Just smoothing the OP source file (without encrypting it at all!) Gets this file , for which Adobe Acrobat even shows these permissions:

Explanation
This is the behavior of Adobe Reader, the PDF viewer that is most likely used by the OP: the permissions tab visible by the OP not only reflects what was or was not prohibited during encryption, but also the limitations of the PDF viewer itself.
It seems that the erroneous perception of OP, using encryption and setting permission bits, can be added to the capabilities compared to unencrypted files. In fact, it's the other way around: Encryption allows you to remove permissions compared to what is allowed for an unencrypted document. By using some of the allowed ALLOW_ * bits, you remove permissions. You get the maximum number of permissions by simply not encrypting the document.
In addition to the permissions of an unencrypted document, a particular PDF viewer may require additional usage rights, which vary by viewer. Such readers in PDF format (primarily Acrobat Reader) are usually quite inexpensive or free, but they do not offer full functionality if the corresponding document does not have the appropriate usage rights.
Use rights can be added with the use rights signatures. The use of such signatures of rights of use typically requires software or services provided by the manufacturer of this PDF viewer.
To add usage rights for Adobe Reader, for example, you can use Adobe Acrobat or some Adobe Lifecycle services.
In this way,
The answers
As a result, we get a PDF file in which page deletion (page deletion) and document layout (document compilation) are not allowed
No. As you can see above, your dest.pdf only prohibits page extraction, and as soon as you stop encryption, even that is allowed.
1 - is iText behaving incorrectly, or is it possible to change this parameter altogether using iText? If so, how (example code)?
This is not a bad iText behavior, this is the behavior of Adobe Reader. Adobe Reader limits its capabilities in general and only removes restrictions on documents with usage rights. These usage rights may only apply to Adobe software.
2 Can these rights be set without a password? So far, we have only seen features for installation permissions always combined with user and owner passwords.
Using encryption is actually counterproductive because it can only be used to remove permissions, not to add them.
Resources
Additional information about the problem obtained from the parallel entry on the itext-questions mailing list :
- sample source file illustrating src.pdf problem
- corresponding result file generated by op dest.pdf code
- Screenshot of the tab for allowing viewing PDF of the OP file for dest.pdf file:
