Should swapchain creation say that the application _must not_ create multiple swapchains?

The docs say

>A native window **cannot** be associated with more than one non-retired swapchain at a time. Further, swapchains **cannot** be created for native windows that have a non-Vulkan graphics API surface associated with them.

and defines

>**Cannot** refers to something the API provides no way for the application to express or accomplish. **Must not** describes something that the application is able to express, but that is not valid use of the API, and will have undefined and potentially unrecoverable consequences.

This definition of **cannot** does not seem to apply to the swapchain case. Should this not be **must not**?

In particular in the case of wayland and X, enforcement of this relies entirely on the application not using the same native window multiple times (possibly across multiple distinct VkSurfaceKHR objects.)