taxonomy term path using two different vocabulary
For your content type, you could set a content path pattern (admin/config/search/path/patterns) that looked something like this:

[node:field_destination]/[node:field_category]/[node:title]

This would put the destination term in front of the category term for your content nodes.  However, there is no good way for you to put the destination term in the path to the category vocabulary, because there might be zero, one or many content type nodes for any given category, and you have no good way to relate these two terms.