Windows server itself can be used to share the storage via iscsi. If it is just one node then I think you can just use it instead of starwind.
I am currently using a similar setup while I restructure my stuff. Have an lsi card passed through to a Windows server vm. Have 6 8tb drives connected to the lsi card and pooled via drive pool to be presented as a single volume. Access is via a single gbe link and I get ~120MBps transfers.
I am not using it for any vm storage though. Just media and backups.
This is an always on media server. Esxi host with HBA passed on to a windows host running drive pool. this host Also runs my VCSA, DNS, unifi, plex and a few other vms. I Just need the storage server here to be able to serve 2 concurrent plex streams and it does that.You don't want your single Windows host as an iSCSI target - it's rather slow (MSFT had no cache for iSCSI), it's not certified for VM hosts (OK, you don't use that but still...), and you make your storage a SPOF.
For backups and some bulk media dump you'd better stick with either NFS or SMB3, block protocols like iSCSI & Co aren't your best friends here
The card is RMS25CB080 6Gb/s SAS/SATA Integrated RAID Module (LSI SAS2208 RAID with 1GB cache)You can't flash a 1GB RAID card to HBA IT mode AFAIK.
pool: ESXI_Storage state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM ESXI_Storage ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/8TB Drive ONLINE 0 0 0 gptid/8TB Drive ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gptid/8TB Drive ONLINE 0 0 0 gptid/8TB Drive ONLINE 0 0 0 logs mirror-1 ONLINE 0 0 0 gptid/250 gb ssd ONLINE 0 0 0 gptid/250 gb ssd ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 gptid/250 gb ssd ONLINE 0 0 0 gptid/250 gb ssd ONLINE 0 0 0