A few things first:
The display names coming from the TimeZoneInfo
object are localized to the operating system's language settings, and you cannot provide a specific language or culture.
They are also inconsistent across platforms. The example you gave is the output when running on Windows, but not on Linux or Mac OSX.
Noda Time doesn't encapsulate display names. Localizations are generally out of scope. So the simple answer to your question is - no.
However, that is (in part) why my TimeZoneNames library exists. It works with IANA or Windows time zone identifiers, and provides localized names for display of time zones in various use cases. You can use it in conjunction with NodaTime, or by itself. For example:
DateTimeZone tz = DateTimeZoneProviders.Tzdb["Australia/Hobart"];
string displayName = TZNames.GetDisplayNameForTimeZone(tz.Id, "en-US");
Console.WriteLine(displayName); // "(UTC+10:00) Hobart"
This will return consistent output across platforms, and gives you full control over the culture used to localize the output.