Why SSIS is a mystic art for many .NET Devs

First a bit about my background might help. I come from a developer background. Specifically, I work as a senior web development on large ASP.NET web sites. I have worked in .NET since just before the release 2.0 (8 years) I have a Information Technology Degree with a Database focus. I largely fell into web development due to its popularity and stayed due to my investment in the platform. SSIS is such a disappointment because it doesn't fit in my world. I instead tack it onto my world with its own set of weirdness sort of like any other framework or language like XML, Regular Expressions, etc

CLR dependency without exposure of capabilities outside of a SSIS package

The SSIS platform was built for BI folks with zero development experience. There is zero carry over with .NET to SSIS. The components from what I have been able to gleam are not reusable by a vanilla .NET application. Want to parse a CSV and show the success and failure rows in a UI? Don't want to introduce a bunch of junk: SSIS package, a table to stage success rows, a table to stage failure rows. Your out of luck. I think, if makers of the black boxes that are SSIS control flow and data flows components would expose the underlying glue as classes that .NET applications could use, we would have one standard mechanism for reading from different sources across the platform. We would also not have to introduce a third type system here is how I am counting: your programming language's type system, SQL Server, SSIS DT_* types. Please correct me if I am wrong. I love to hear a bout it.

SSIS uses Windows Workflow well kinda

If Microsoft had such an investment in Windows Workflow (WF), why did they make BIDS now SSDT. It would of been a good story to make SSIS Catalog on SQL Server as one way to host WF with an SSIS being a implementation of WF Framework. Open source it to show how it can be done. Also if you want to use say a Flat file data source in your WF package but outside of SSIS, why not?

Conclusion

I know this is kind of a rant. I know there are more low level ways to do most of what BIDS now SSDT does in .NET. I think the correlation between the two technologies could be cleaner and more transparent. I get BI Developers just want to shell in occasionally to .NET with a Script task. I think it would increase SSIS usage if there was a clear platform independence for some features of SSIS. Need to shred a Excel document in SSIS or your backend .NET application. Let's have a way to pull away the GUI and interact with the Excel document shredder directly and consistently in both applications.