This is quite normal, (if a little unexpected, till you know why).
It's because anything that is not a standard disk or network resource uses a plug-in, and the socket for the plug-in/s is (only) on the 'right-hand-side' of the code (because 'way back when', your Source was normally always the standard disk/network resource, and it was always the Destination - if anything - that was required to be something different, e.g, FTP).
So, when you select a profile type to back up from such a non-standard resource, we have to re-wire the profile, so that it maintains this orientation (non-standard resource is on the right) but data is then set to flow from right to left, to enable what you want to achieve.
If you create the profile from the New Profile wizard, it will do this for you automatically, and swap/rename the Labels that state (inside the Modify view) which side is connected to what, and the orientation of the display.
We can do this inside the Modify view (because we're only displaying one profile, so we can change things around). But when displaying all profiles (such as in the main UI), we have to apply one set of rules to all profiles, so such a profile will display the FTP side as Right/Dest and your local disk as Left/Source, yes (because inside the code, that is true: local disk is indeed on the left of the code, but the data is correctly flowing to it, not from it). If you Modify the profile and check the Description pane on the Simple page that opens by default, it will correctly display the actions the profile will perform.
Note also that the icon in the Type column has the arrow (direction) reversed, showing it is copying Right to Left.
Bear in mind that other 'side-specific' aspects in the main UI may 'follow' this reversal - for example, right-clicking such a profile > Open Left/Source will open the resource listed under the Left/Source column (in this case, your hard disk). And so on.
It's almost certainly never going to change, because to do so would require a complete re-write to make each 'side' of the code identical, which would be an enormous job. We simply don't have the time, given that it's a 'cosmetic' thing. If we were starting from scratch, that would be different, but we're not...
It's because anything that is not a standard disk or network resource uses a plug-in, and the socket for the plug-in/s is (only) on the 'right-hand-side' of the code (because 'way back when', your Source was normally always the standard disk/network resource, and it was always the Destination - if anything - that was required to be something different, e.g, FTP).
So, when you select a profile type to back up from such a non-standard resource, we have to re-wire the profile, so that it maintains this orientation (non-standard resource is on the right) but data is then set to flow from right to left, to enable what you want to achieve.
If you create the profile from the New Profile wizard, it will do this for you automatically, and swap/rename the Labels that state (inside the Modify view) which side is connected to what, and the orientation of the display.
We can do this inside the Modify view (because we're only displaying one profile, so we can change things around). But when displaying all profiles (such as in the main UI), we have to apply one set of rules to all profiles, so such a profile will display the FTP side as Right/Dest and your local disk as Left/Source, yes (because inside the code, that is true: local disk is indeed on the left of the code, but the data is correctly flowing to it, not from it). If you Modify the profile and check the Description pane on the Simple page that opens by default, it will correctly display the actions the profile will perform.
Note also that the icon in the Type column has the arrow (direction) reversed, showing it is copying Right to Left.
Bear in mind that other 'side-specific' aspects in the main UI may 'follow' this reversal - for example, right-clicking such a profile > Open Left/Source will open the resource listed under the Left/Source column (in this case, your hard disk). And so on.
It's almost certainly never going to change, because to do so would require a complete re-write to make each 'side' of the code identical, which would be an enormous job. We simply don't have the time, given that it's a 'cosmetic' thing. If we were starting from scratch, that would be different, but we're not...