The difference is mainly the Device Type that is pre-filled in the field, and delivery formats that will work on that particular app.. You can pick a profile that matches the target software token app Device Type, or hand type the Serial, or blank it, or use any profile and hand write your own...as long as it matches something seen on the token app itself:
It is mainly about categorizing for reporting: How many tokens are distributed to what version of RSA token app, but the functionality of the token itself is the same across all versions (6-8 digit, pin type, interval...).
Also, profiles prevent you from picking delivery options that do not work, for example CTF or QR won't work...but you could pick an Android profile and choose .sdtid and it would load on RSA software token for windows as long as the serial number or type was also accurate. You could pick Android CTKIP as well, but you'd have to hand-change the CTKIP URL to fit the URL type the RSA software token app for windows understands....
