I think the unhelpful answer is, "Sure. You do some arithmetic and there you go." The helpful answer is probably, "Nope, there is no built-in language function that accepts a DispatchTime (or even a dispatch_time_t) and gives you back a Date that would agree with your understanding of a clock/calendar on the wall."
From the documentation of DispatchTime: "A point in time relative to the default clock, with nanosecond precision." A close look at DispatchTime reveals that it's a UInt64, so that means it's probably a number of nanoseconds. Date has an initializer that accepts a TimeInterval, but that's a) a Double and b) a number of seconds and c) relative to either the reference date or the Unix epoch.
So, you get to figure out what's the zero time for "the default clock", then do some math to figure out how to transform nanoseconds after that into seconds after the appropriate reference time and then you can call the appropriate Date initializer.
Or, I guess, you can get the DispatchTime.now value and compare it to your dispatch time that the API gave you and then do what you want with the delta (which is in nanoseconds).