PC players here. Outside of the initial boot time which massive has mentioned is on their side and being worked on, I fast travel almost instantly.
Not sure how much it effects things on the console side. But it should in theory make some sort of a difference moving from a spinning drive.
My games and windows run off nvme Samsung pro(in the m.2 slot not pci-e) drive if that info assist at all.
I got one specifically for this game with an X.B.O.X I am almost 100% of the time the first to load into anything and my connection is generally meh. So from my perspective it is doing wonders. On my regular xbox one, I was always like 20-30 seconds behind everyone in division 1. It also seems to help just about every function of the game. Textures have very few glitches, sound is much more responsive, and I don't remember any invisible walls since the upgrade. how much is the X and how much is the SSD not sure, but I fear the day I might ever find out....
i put a SSHD 2 TB in my PS4 Pro, cost like 80€ from amazon. pure SSD is not worth the investment.
google can help you there, threre are many benchmarks. it wont even void the warranty, sony is cool that way.
i also play mostly on PC and simply put: i can not and will never understand why you would not game on an SSD.
you download 40+ GB for this game and expect a HDD to deliver the textures?
what year is this? i bought a NVMe m.2 with 1000GB for 200€ anyone who thinks it would not make the most difference ever has another bottleneck somewhere else.
I put a 1 Tb Crucial MX500 SSD in my PS4 Pro costing around £100 from Crucial.com direct as Amazon wanted to charge £25 import tax to the UK and it has really livened up the game, I now teleport rapidly reducing the travel time well over 50%, I can teleport back to a safe house for a restock and it's so fast, before it was a chore to wait so long. I have saved the team several times due to being able to respawn in so quickly after dying when the whole team has wiped, once that countdown has finished a couple of seconds and I'm back in.
Textures are always loaded unlike before where the trees and details on buildings would often take a couple of seconds to catch up. I feel the game and character movements are snappier and more fluid than before and the graphics just look fresher, but that may be my imagination. In the PS menus the lists are loaded in as I scroll with no waiting unlike before when scrolling down my friends list and having to wait ages for the list to fill in now it's just there!
I don't know if Ubisoft Devs cater for SSD's in the Division 2 as there are no doubt some features on an SSD not being used during the game and for that reason there are more cost effective solutions than SSD like hybrid SSHD, but I hope they realise an increasing number of players are using them, and it's rumoured that PS5 will be shipped with SSD as standard, so now is a good time for trial development on us SSD players.
For those players who do not have SSD, I would recommend rebuilding the PS4 database regularly as this is in effect a defrag of the hard disk and will help with disk access times and speed up the loading times of textures and teleporting.
I will at some point replace the SSD with the original HD and sell the PS4 Pro and use the SSD in another PC or old laptop so I get long term value out of my purchase.
It is easy to determine if an SSD or NVMe would result in faster completion of any given workload.... by taking compute resource measurements while that workload is running. We can all guess that when fast travelling, the wait is for the new area to load its texture resources from disk. You cane use windows task manager performance tab, resource monitor, or even performance monitor to see disk utilization and queue length. If disk utilization is high, like peaks to 100% and/or queue length gets up into the 1 range, then you can expect that work to complete faster if disk IO is improved with better hardware.
If the bottleneck is elsewhere, throwing SSD at it won't help. And if there is no bottleneck from compute resource limitations, then it is the code.
I haven't taken measurements, but would venture a guess that the fast travel time is mostly disk IO bound. But I would never recommend hardware upgrades without taking some measurements first.