D8: The same content type, but different url path aliases pattern based on paragraphs. Possible?
Since you mention that you only have a single allowed paragraph, something like [node:paragraph_field:entity:type:target_id] might work, but untested. That will use the machine name of the referenced paragrap type.

If not, you can always implement a custom token on nodes and then do whatever you want using hook_token_info() and hook_tokens().

I also agree with others that this seems like a somewhat strange architecture and usually list/term fields are used for such a categorization, this will most likely also work better if you ever need to do something like an exposed filter in a view and so on.